Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ADScanPro/Claude-ADWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/adscanpro/claude-ad/ad-recon)<a href="https://agentmods.dev/commands/adscanpro/claude-ad/ad-recon"><img src="https://agentmods.dev/badge/commands/adscanpro/claude-ad/ad-recon.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.00380 |
| Opus 5 | $0.00023 | $0.00190 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
ad-recon scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Run reconnaissance / collection against $1.
Authorized engagements only. This reads the scope defined by /ad-scope; if
./ad-engagement/scope.md does not exist, tell the operator to run /ad-scope $1
first and stop.
Steps:
-
Read
./ad-engagement/scope.mdand confirm the domain $1, DC IP, and the credentials/privilege level to use are present. Surface any forbidden actions the client set. -
Launch the ad-enumerator agent with that scope. It runs the collection phase with standard tools (netexec/nxc, impacket, rusthound-ce or bloodhound-python for the BloodHound CE graph, certipy find) and follows
ad-methodology,ad-environment-constraintsandad-opsec-telemetry. -
Collection is read-only. The enumerator must not modify the directory; if the scope forbids specific enumeration (for example loud BloodHound collection), respect it.
-
When the agent returns, save its structured inventory under
./ad-engagement/and print a short summary: counts of users/groups, kerberoastable and AS-REP-roastable accounts, vulnerable ADCS templates, interesting ACLs, trusts, and the BloodHound CE zip path.
Do not plan or execute a path here. Next step is /ad-attack-paths $1.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 34 lines · 46 tokens per session scan A ea99a9ce0c51
ad-recon is a command published in the GitHub repository ADScanPro/Claude-AD (165 stars, last pushed 13d ago), licensed MIT. It adds 46 tokens to every session and 380 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
hunt
Active Directory offensive phase — credential attacks (spray if allowed), AS-REP and Kerberoast workflows, NTLM relay opportunities, delegation abuse paths, ACL-based escalation, AD CS template abuse, lateral movement within ROE. Usage: /hunt corp.local.
recon
Active Directory reconnaissance — DNS SRV/LDAP DC discovery, LDAP user and group enumeration, Kerberos pre-auth and AS-REP candidates, SPN discovery for Kerberoasting, SMB signing and null session policy, password policy, trust relationships, BloodHound/SharpHound collection prep. Requires ROE. Usage: /recon…
autopilot
Phased autonomous checklist for AD engagements within ROE — not unsupervised internet-wide scanning. Usage: /autopilot corp.local --normal.
chain
Build multi-hop Active Directory attack paths — combine AS-REP, Kerberoast, delegation, ACL abuse, AD CS, lateral steps into one narrative. Usage: /chain.
intel
Domain controller and Windows Server build intel — patch level, known abuse techniques relevant to version, planning prioritization. Usage: /intel corp.local.
scope
Rules of engagement — verify authorized domains, DCs, subnets, accounts, destructive actions, and exclusions before testing. Usage: /scope or /scope corp.local.