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/evaluris-solutions/claude-active-directory/chaingit clone --depth 1 https://github.com/Evaluris-Solutions/claude-active-directoryWrote 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/evaluris-solutions/claude-active-directory/chain)<a href="https://agentmods.dev/commands/evaluris-solutions/claude-active-directory/chain"><img src="https://agentmods.dev/badge/commands/evaluris-solutions/claude-active-directory/chain.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.00000 | $0.00314 |
| Opus 5 | $0.00000 | $0.00157 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
chain 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 33 lines · 0 tokens per session scan A 1ca981e668ef
chain is a command published in the GitHub repository Evaluris-Solutions/claude-active-directory (16 stars, last pushed 4mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 314 tokens. 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
ad-scope
Define and record the scope of an authorized Active Directory engagement (domain(s), DC IP, initial credentials, and what is in scope) into a scope file the other AD commands read.
ad-attack-paths
Launch the ad-attack-planner agent to reason low-privilege-to-Domain-Admin paths from the collected inventory and BloodHound CE graph, then present the plan for human approval before any exploitation.
ad-recon
Launch the ad-enumerator agent to run the collection phase against the defined scope, producing a structured AD inventory (users, groups, SPNs, ACLs, ADCS templates, trusts) plus a BloodHound CE graph.
aod.project-plan
Create implementation plan with dual sign-off (PM + Architect) - Streamlined v2.
aod.document
Quality review — code simplification, docstrings, CHANGELOG, API docs (supports --autonomous).
tachi.architecture
Generate an architecture description for tachi threat modeling input.