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 stark-ai-de/agent-skills --skill docs-auditgit clone --depth 1 https://github.com/stark-ai-de/agent-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/stark-ai-de/agent-skills/docs-audit)<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/docs-audit"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/docs-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/stark-ai-de/agent-skills/docs-audit"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/docs-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.00046 | $0.00596 |
| Opus 5.5 | $0.00018 | $0.00238 |
| Sonnet 5.5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
docs-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Audit
Goal
Find documentation gaps that block users, contributors, maintainers, or agents from understanding, installing, validating, and safely changing the repository.
When to use
- The user asks whether docs are clear, complete, current, or public-ready.
- README, examples, onboarding, API docs, or contribution docs need review.
- Documentation promises may have drifted from actual code and commands.
When not to use
- The user asks for a full repo maintenance audit; use
repo-health-audit. - The user wants release notes; use
release-manager. - The user wants prose editing only and no repo evidence check.
Inputs to inspect
- README, docs, examples, changelog, contributing guide, security policy, and license.
- Package scripts, CLI help, config examples, and source files that docs mention.
- Internal links, install commands, screenshots, and generated docs.
Review rubric
Check audience fit, first-run path, command accuracy, link integrity, examples, maintenance docs, public safety, and agent usability. Read references/docs-rubric.md for details.
Workflow
- Identify the intended audiences and main user journeys.
- Compare README promises with actual files and commands.
- Verify install, validate, and usage examples where practical.
- Check internal links and stale references.
- Separate user-facing docs gaps from maintainer-only improvements.
- Produce a prioritized docs gap list.
Safety rules
- Do not publish docs, rewrite policy, or change public support commitments without approval.
- Do not include private URLs, internal hostnames, customer details, or credentials in examples.
- Mark commands as unverified when they were not run.
References
Read only when needed:
references/docs-rubric.md
Scripts
No bundled scripts.
Output format
Return:
- Summary
- Blocking docs gaps
- Confusing or stale sections
- Missing examples
- Suggested rewrite or new docs
- Recommended next action
Failure modes
What ships with it
1 file 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.
- 1mo ago First seen · 87 lines · 46 tokens per session scan A ab3edf0305b4
docs-audit is a skill published in the GitHub repository stark-ai-de/agent-skills (8 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 596 once invoked, about $0.0002 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
claude-delegate
Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the claude CLI — for example, "have another Claude implement…
warp-delegate
Delegate a coding task to the Warp Agent CLI (oz) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Warp - phrasings like "have Warp implement X", "delegate this to the Warp CLI", "run it through Warp", "use oz to…
zcode-delegate
Delegate a coding task to the Z.AI ZCode CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to ZCode — phrasings like "have ZCode do X", "delegate this to ZCode", "run it through ZCode", or "use ZCode to implement/fix/refactor" — or…
cline-delegate
Delegate a coding task to the Cline coding agent CLI (cline) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Cline - phrasings like "have Cline implement X", "delegate this to cline", "run it through Cline", or "use cline to…
kimi-delegate
Delegate a coding task to the Kimi Code CLI (kimi) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Kimi - phrasings like "have Kimi implement X", "delegate this to Kimi", "run it through Kimi Code", or "use Kimi to…
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.