Borrowing it
Nothing to install: this file belongs to carmentacollective/carmenta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/carmentacollective/carmenta/main/.claude/commands/documentation-audit.mdgit clone --depth 1 https://github.com/carmentacollective/carmentaWrote 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/carmentacollective/carmenta/documentation-audit)<a href="https://agentmods.dev/commands/carmentacollective/carmenta/documentation-audit"><img src="https://agentmods.dev/badge/commands/carmentacollective/carmenta/documentation-audit/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/carmentacollective/carmenta/documentation-audit"><img src="https://agentmods.dev/badge/commands/carmentacollective/carmenta/documentation-audit.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.00026 | $0.00932 |
| Opus 5.5 | $0.00010 | $0.00373 |
| Sonnet 5.5 | $0.00005 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
documentation-audit 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 2mo 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.
- 2mo ago First seen · 144 lines · 26 tokens per session scan A 9e0de60e2ef0
documentation-audit is a command published in the GitHub repository carmentacollective/carmenta (2 stars, last pushed 4mo ago), with no licence file. It adds 26 tokens to every session and 932 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
qa
Use when performing local QA review before pushing PR changes. Evaluates test coverage, error handling, and code quality.
roadmap
Use when performing local roadmap review before pushing PR changes. Assesses strategic alignment, feature scope, and user value.
security
Use when performing local security review before pushing PR changes. Scans for vulnerabilities, secrets exposure, and security anti-patterns per OWASP Top 10.
architect
Use when performing local architecture review before pushing PR changes. Reviews design patterns, system boundaries, coupling/cohesion, and ADR compliance.