AD OPSEC Telemetry

AD OPSEC Telemetry is a Quality skill for Claude Code, published by ADScanPro in Claude-AD.

176 stars28 forkson ADScanPro/Claude-ADAdded 2026/09/08+5% in starsRepository updated 2026/08/24

active-directoryactive-directory-securityadcsbloodhoundclaudeclaude-codeclaude-code-pluginclaude-skillsdcsynckerberoastingkerberosntlm-relayoffensive-securitypenetration-testingpentestingred-team

Install in seconds

Install AD OPSEC Telemetry

Copy AD OPSEC Telemetry into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/ADScanPro/Claude-AD/tree/main/skills/ad-opsec-telemetry ~/.claude/skills/ad-opsec-telemetry

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/ADScanPro/Claude-AD.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/ad-opsec-telemetry/SKILL.md in ADScanPro/Claude-AD
Installs to: ~/.claude/skills/ad-opsec-telemetry
Collection: One of 8 skills cataloged from this repository
Category: Quality — 1897 skills

What AD OPSEC Telemetry does

AD OPSEC Telemetry explains the Windows events and defender alerts generated by common Active Directory techniques like Kerberoasting, AS-REP roasting, DCSync, LSASS dumping, and lateral movement. Use it to document engagement noise or to decide what to monitor.

AD OPSEC Telemetry is cataloged under Quality on DirSkills. AD OPSEC Telemetry comes from a repository tagged active-directory, active-directory-security, adcs, bloodhound and claude.

Documentation

README

Excerpt

AD OPSEC and Telemetry

Every technique leaves a trace. The goal here is not evasion. It is knowing the noise profile of each action so you can document it for the client before the engagement, pick the quieter of two functionally equivalent techniques, and correlate what you did with what their SOC saw. For a defender, read the same tables backwards: they are the events to monitor and alert on.

Two rules of engagement throughout:

Document the noise. Tell the client what each high-signal action generated, with the event ID and the source IP, so they can find it in their logs.
Coordinate the loud ones. DCSync, mass spraying, coercion at scale, and LSASS dumps need explicit client sign-off or an end-of-engagement window when detection no longer matters.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about AD OPSEC Telemetry

What else does ADScanPro publish alongside AD OPSEC Telemetry?
AD OPSEC Telemetry is one of 8 skills that DirSkills catalogs from ADScanPro/Claude-AD, the repository it ships in. Its siblings there include AD CS Attacks, AD Environment Constraints and AD Methodology. Each one is a separate skill with its own page in this directory, installs the same way AD OPSEC Telemetry does, and is maintained by ADScanPro in that same repository. The rest of the collection is listed on the ADScanPro/Claude-AD page.
How does AD OPSEC Telemetry compare to other Quality skills?
AD OPSEC Telemetry ranks #1690 by stars among the 1897 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of AD OPSEC Telemetry against them. Open each page to compare what they document and how they install.