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 skills add int2t05/engineering-skills --skill documentation-auditgit clone --depth 1 https://github.com/int2t05/engineering-skillsWrote 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/skills/int2t05/engineering-skills/documentation-audit)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/documentation-audit"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/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/skills/int2t05/engineering-skills/documentation-audit"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/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.00027 | $0.00314 |
| Opus 5.5 | $0.00011 | $0.00126 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
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 14d 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
Documentation Audit
When to use
- Write or synchronize implementation documentation with source evidence.
Not for: spec for requirement changes; oss-polish for presentation.
Steps
-
Agree readers, purpose, scope and paths; inventory actual documents rather than assuming five mandatory categories.
-
Trace contracts, configuration and meaningful calls; distinguish stale descriptions from missing implementation.
-
Correct descriptive drift and ask about requirement or design discrepancies rather than rewriting agreed intent to excuse code.
-
Produce readable docs and the approved report with evidence, fixed items and open decisions; check paths, examples and symbols.
Output: Suggested paths, subject to human audit: docs/audit/YYYY-MM-DD-documentation.md at the approved path alongside corrected docs.
Verify
- Descriptions match source evidence; requirement changes were not silently accepted and review status is honest.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- human-audit.md — document consent, readability and human review.
- references/templates.md — audit-report template
- references/writing-docs.md — writing new documentation from scratch (README, feature docs, API docs)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed · -70 lines · -50 tokens per session 65d75c1aaf17
- 21d ago Changed · +1 lines 3f7b1bd6c884
- 2mo ago First seen · 105 lines · 77 tokens per session scan A 77a83efb54c4
documentation-audit is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 15d ago), licensed MIT. It adds 27 tokens to every session and 314 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 skills, from other repositories
context-review
Skill "context-review" from morodomi/dev-crew, covering context review, usage, workflow, question categories and resolution values.
flask-quality
A quality-check workflow for Flask applications, a Python web framework. It runs tests, strict type checks, and code-formatting checks.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
ring:running-dev-cycle
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIALID and data path.