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 skills/conn-castle/agent-layer/audit-documentationnpx skills add conn-castle/agent-layer --skill audit-documentationgit clone --depth 1 https://github.com/conn-castle/agent-layerWhat 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.00030 | $0.00462 |
| Opus 5 | $0.00015 | $0.00231 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
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 3d 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
audit-documentation
Audit Markdown against repository evidence; fix safe inaccuracies.
Scope
- Use supplied scope; otherwise audit all tracked
*.mdfiles. - Exclude ISSUES.md, BACKLOG.md, DECISIONS.md, COMMANDS.md, and
CONTEXT.md. Use
/audit-memorywhen the user requests memory files. - A finding limit caps reporting, not coverage. Empty scope returns
no-findings.
Contract
- Validate actionable claims against files, configuration, symbols, scripts, and contracts. An unexecuted command is not verified behavior.
- Fix the smallest evidence-backed error that could materially mislead. If docs express better intended behavior than code, report a code gap. Preserve ambiguous content and name the missing decision.
- Do not edit source, tests, memory files, or product policy.
Workflow
Record scope and inspect enough context to establish its claims. For large scopes, parallelize non-overlapping read-only investigations; the owning agent validates candidates, resolves conflicts, and edits.
Check:
- referenced commands, paths, configuration keys, and interface names
- architecture and workflow claims against current code and configuration
- contradictions, renamed concepts, and drift across in-scope documents
- templates or examples that disagree with their canonical source
Mark statically indeterminate claims unverified. Ignore style, fix supported inaccuracies, and leave code gaps or unresolved intent unchanged. Do not log the audit to memory.
Write a concise summary with:
# Documentation Audit Summary— scope and verdict## Fixes Applied## Code Gaps## Decisions Needed
Findings include severity, location, evidence, impact, outcome (fixed,
code-gap, or needs-user-decision), and type (command, path, config,
interface, architecture, or cross-doc). Use None for empty sections.
Finish when every document is checked and every material finding has an outcome.
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.
- 3d ago First seen · 57 lines · 30 tokens per session scan A 0468e77bae8f
audit-documentation is a skill published in the GitHub repository conn-castle/agent-layer (10 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 462 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-31.
Other skills, from other repositories
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.