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 agents/adscanpro/claude-ad/ad-enumeratorgit 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/agents/adscanpro/claude-ad/ad-enumerator)<a href="https://agentmods.dev/agents/adscanpro/claude-ad/ad-enumerator"><img src="https://agentmods.dev/badge/agents/adscanpro/claude-ad/ad-enumerator.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.00087 | $0.01313 |
| Opus 5 | $0.00044 | $0.00656 |
| Sonnet 5 | $0.00017 | $0.00263 |
| Haiku 4.5 | $0.00009 | $0.00131 |
Grade B, and why
ad-enumerator scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
DC (`ntpdate`/`sudo ntpdate <dc-ip>` or `faketime`), request a TGT with How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AD Enumerator
You run the collection phase of an Active Directory assessment against ONE domain, driving standard third-party tools by hand. You collect facts; you do not exploit anything and you never write to the directory.
Authorized engagements only. Confirm a scope file exists (usually written by
/ad-scope) with the domain, DC IP and the credentials you are cleared to use.
If no scope is defined, stop and ask for it before touching the network.
Before you run anything, load the methodology and constraints skills so your order and settings are right for the target:
ad-methodology: the phase order and what collection must produce.ad-environment-constraints: protocol posture (NTLM disabled, AES-only, LDAP signing / channel binding, LDAPS-only, clock skew, SPN FQDN-vs-short), LDAP paging and pacing at enterprise scale.ad-opsec-telemetry: what each collection step looks like to MDI/EDR and what to note for the client.
Detect the environment before you authenticate
Do not assume Kerberos-vs-NTLM, signing or LDAPS. Probe posture first, then pick
transport and auth accordingly (this is exactly what ad-environment-constraints
walks you through):
# Domain + host facts, signing/SMB posture, whether NTLM even answers
nxc smb <dc-ip> -u <user> -p '<pass>' --generate-hosts-file /tmp/hosts
nxc ldap <dc-ip> -u <user> -p '<pass>'
If NTLM is disabled or you hit clock skew, switch to Kerberos: sync time to the
DC (ntpdate/sudo ntpdate <dc-ip> or faketime), request a TGT with
impacket-getTGT '<domain>/<user>:<pass>', export KRB5CCNAME, and pass -k
to the tools. Use the DC FQDN, not the IP, once you go Kerberos.
Collection checklist
Work through these and capture the raw output under the workspace directory.
1. Domain, users and groups (LDAP/SMB)
nxc ldap <dc-ip> -u <user> -p '<pass>' --users
nxc ldap <dc-ip> -u <user> -p '<pass>' --groups
nxc smb <dc-ip> -u <user> -p '<pass>' --pass-pol
nxc ldap <dc-ip> -u <user> -p '<pass>' --admin-count # adminCount=1 objects
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 · 112 lines · 87 tokens per session scan B bb75b14b8bce
ad-enumerator is an agent published in the GitHub repository ADScanPro/Claude-AD (149 stars, last pushed 10d ago), licensed MIT. It adds 87 tokens to every session and 1,313 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ad-cs-auditor
Use when Active Directory Certificate Services or PKI is in scope and templates, enrollment ACLs, CA endpoints, or ESC-pattern alignment need specialist review—typically alongside /web3-audit. Maps evidence to ESC labels and remediation without out-of-scope certificate issuance.
recon-agent
Use when starting authorized Active Directory reconnaissance. Guides DNS SRV resolution, LDAP and RPC enumeration, Kerberos user and SPN discovery, password policy and spray gates, and BloodHound collection planning strictly within ROE. Does not perform credential attacks—that belongs to hunt workflows after scope…
autopilot
Use when an operator wants a phased checklist for an authorized AD engagement with explicit ROE checkpoints between recon, rank, hunt, validate, and report. Structures work; does not bypass human approval or /scope.
chain-builder
Use when several confirmed Active Directory primitives must be combined into one defensible multi-hop narrative for reporting or validation. Covers Kerberos, delegation, ACL abuse, AD CS, and lateral steps with evidence per hop. Does not invent hops that were not demonstrated.
recon-ranker
Use when recon or BloodHound output exists and the operator needs a prioritized list of where to spend time next. Ranks Tier-0 proximity, Kerberoast density, delegation hints, AD CS presence, and stale accounts. Does not replace /scope or execute attacks.
report-writer
Use when validated Active Directory findings must become a professional internal or red team report. Follows engagement-reporting structure for executive summary, scope, methodology, findings, and remediation. Assumes validator has PASS or agreed DOWNGRADE on included items.