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.
npx agentmods add commands/adscanpro/claude-ad/ad-scopegit 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-scope)<a href="https://agentmods.dev/commands/adscanpro/claude-ad/ad-scope"><img src="https://agentmods.dev/badge/commands/adscanpro/claude-ad/ad-scope.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 | $0.00037 | $0.00461 |
| Opus 5 | $0.00018 | $0.00230 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
ad-scope 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 4d 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
Define the scope for an authorized Active Directory assessment.
Domain: $1 DC IP (if given): $2
Authorized engagements only. This file is what every later step trusts as its boundary. Fill it from what the client authorized in writing; do not widen it.
Do the following:
-
If any of these are missing, ask the operator for them before writing:
- Domain(s) / forest and their functional level, if known.
- DC IP(s) and DC FQDN(s).
- Initial credentials you are cleared to use (user + password or hash, or a Kerberos ccache). Note the privilege level (assume low-priv unless told).
- In-scope hosts / subnets and anything explicitly out of scope.
- The objective (for example, path to Domain Admin) and any actions the client forbids (no password resets, no coercion, no DCSync, business-hours only).
- Engagement window and a client point of contact for stop/rollback.
-
Do a light reachability check only against the DC IP the client gave you, and do not scan anything not yet in scope:
nxc smb $2 2>/dev/null || echo "DC not reachable / not yet provided" -
Write a scope file the other commands will read, at
./ad-engagement/scope.md(create the directory). Record everything above plus the date and the operator. Keep credentials only as the engagement requires and note where they are stored; do not paste secrets anywhere they should not live. -
Print a short confirmation of the recorded scope and the explicit out-of-scope and forbidden-action list, so it is visible before recon starts.
Do not enumerate or exploit here; scope only. Next step is /ad-recon $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.
- 4d ago First seen · 43 lines · 37 tokens per session scan A f9cbac91ac50
ad-scope is a command published in the GitHub repository ADScanPro/Claude-AD (141 stars, last pushed 9d ago), licensed MIT. It adds 37 tokens to every session and 461 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.