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/chankov/agent-fleetWrote 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/chankov/agent-fleet/audit-documentation)<a href="https://agentmods.dev/commands/chankov/agent-fleet/audit-documentation"><img src="https://agentmods.dev/badge/commands/chankov/agent-fleet/audit-documentation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/chankov/agent-fleet/audit-documentation"><img src="https://agentmods.dev/badge/commands/chankov/agent-fleet/audit-documentation.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00304 |
| Opus 5.5 | $0.00000 | $0.00122 |
| Sonnet 5.5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
audit-documentation 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 20d 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
Command: Audit documentation consistency
Use when reviewing a selected documentation scope for consistency. Inputs: requested files or documentation area; optional accepted decision or change to check against. This command is read-only and authorizes no external actions.
Disposition: extract evidence-backed auditing; exclude mandatory document taxonomy, paths, and automatic consolidation.
Process
- Discover the target documentation index, canonical sources, applicable policy, and requested scope. Ask if scope cannot be resolved; do not silently audit the whole repository.
- Check local links and anchors with existing tooling where available. Distinguish broken references from unavailable external targets; do not fetch external links without appropriate authorization.
- Find orphaned pages relative to the target's indexing policy, duplicated guidance, and contradictory current instructions. Historical decisions, generated copies, and examples are not automatically conflicting current policy.
- Compare claims with relevant implementation, tests, and accepted decisions where accessible. Cite both sides of each conflict and separate confirmed findings from suspected ones.
- Suggest canonical owners and focused corrections using target evidence. Where ownership is unresolved, present a question rather than choosing silently. Do not edit, delete, or consolidate files.
Output and done when
Report inspected scope, findings with file/section evidence, suggested canonical owners, and proposed corrections. List inaccessible sources and unchecked areas explicitly. Completion means the requested audit is reported, not that every document is correct or that fixes have been applied.
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.
- 20d ago First seen · 20 lines · 0 tokens per session scan A bc9c0b609d07
audit-documentation is a command published in the GitHub repository chankov/agent-fleet (19 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 304 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-09-27.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.