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 me2resh/apexyard --skill docs-auditgit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/docs-audit)<a href="https://agentmods.dev/skills/me2resh/apexyard/docs-audit"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/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/me2resh/apexyard/docs-audit"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/docs-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.01621 |
| Opus 5.5 | $0.00014 | $0.00648 |
| Sonnet 5.5 | $0.00007 | $0.00324 |
| Haiku 4.5 | $0.00003 | $0.00162 |
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 4d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing: read docs/skills/shared/writing-rule.md before you write a durable artifact.
/docs-audit — Documentation Completeness (Diataxis)
Deep-dive documentation analysis using the Diataxis framework. Checks that docs cover all four quadrants (tutorials, how-to guides, reference, explanation) and are not stale. Invoke when /launch-check's documentation row shows WARN or FAIL.
Diataxis Framework
| Quadrant | Purpose | What to look for |
|---|---|---|
| Tutorials | Learning-oriented, guided first steps | Getting started guide, quickstart, "Hello World" |
| How-to guides | Goal-oriented, solving specific problems | Deployment guide, migration guide, troubleshooting |
| Reference | Information-oriented, accurate description | API docs, config reference, CLI flags, environment variables |
| Explanation | Understanding-oriented, why things work | Architecture overview, design decisions (AgDRs), ADRs |
Process
Step 1: README quality
Check README.md for these sections (each is pass/fail):
| Section | Present? | Quality check |
|---|---|---|
| Project description | One paragraph explaining what this is and who it's for | |
| Prerequisites | Language version, tools needed, accounts required | |
| Quick start | Copy-pasteable commands to get running locally in < 5 minutes | |
| Development setup | How to set up the dev environment, run tests, lint | |
| Deployment | How to deploy to staging and production | |
| Contributing | How to contribute (branch naming, PR process, code standards) | |
| License | License type and link |
Step 2: API documentation (if applicable)
- Check for OpenAPI / Swagger spec (
openapi.yaml,swagger.json) - Check for auto-generated docs (Swagger UI, Redoc, tsdoc, typedoc)
- Check if endpoints in the code match the spec (any undocumented endpoints?)
- Check for example requests and responses
Step 3: Operational docs
- Deployment guide: how to deploy, what environment variables are needed
- Runbook: what to do when things go wrong (overlap with
/monitoring-audit) - Changelog: is there a CHANGELOG.md? Are releases documented?
- Architecture overview: high-level diagram or description of components
- AgDRs/ADRs: are technical decisions documented?
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.
- 4d ago Changed · -2 lines b3a99eb6f2d5
- 1mo ago Changed · +4 lines cb97f50ab3b3
- 1mo ago First seen · 139 lines · 35 tokens per session scan A 9290e9a77b70
docs-audit is a skill published in the GitHub repository me2resh/apexyard (533 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,621 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…