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 yeaight7/agent-powerups --skill doc-consistency-checkgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/doc-consistency-check)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/doc-consistency-check"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/doc-consistency-check/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/yeaight7/agent-powerups/doc-consistency-check"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/doc-consistency-check.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.00042 | $0.00686 |
| Opus 5.5 | $0.00017 | $0.00274 |
| Sonnet 5.5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
doc-consistency-check 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Documentation rots when code changes. This check finds stale references in Markdown files — paths, commands, package scripts, env names, links — and flags them for immediate correction.
When to Use
- After a refactor that renamed or moved files, scripts, or env vars
- A reader followed the docs and a command or path failed
- Periodic doc hygiene before a release
Inputs
- The documentation set (Markdown files across the repo, not just the README)
- The current repo state to validate against
Workflow
-
Inventory the docs and extract referenced paths:
git ls-files "*.md" # full doc inventory rg -no "[A-Za-z0-9_-]+/[A-Za-z0-9_./-]+\.[a-z]{2,4}" README.md docs/ # path-like references -
Verify referenced files still exist in the repository. If not, the documentation is stale:
test -f src/components/Button.tsx || echo "STALE: src/components/Button.tsx" -
Verify documented commands against reality. Package scripts, CLI invocations, and env names must match the current source:
rg -no "npm run [a-z:-]+" README.md docs/ | sort -u # documented scripts... rg -n "\"scripts\"" -A 20 package.json # ...vs actual scripts rg -no "[A-Z][A-Z0-9_]{3,}=" docs/ | sort -u # documented env names vs config source -
Check code blocks in documentation. Do the function names and variable names still match the actual source code?
rg -n "functionNameFromDocs" src/ || echo "identifier not found in source" -
Check links. Relative links must resolve to existing files; flag external links that obviously moved.
-
Flag everything for immediate correction. Fix in place when the right value is unambiguous; report the rest with file and line.
Output
- A stale-reference report grouped by type (paths, commands, scripts, env names, links), each with doc file:line
- Fixes applied where the correct replacement is unambiguous
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 · 72 lines · 42 tokens per session scan A 5f39b6c72a11
doc-consistency-check is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 42 tokens to every session and 686 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-09-14.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
simplify-code
Sequential 3-lens cleanup of recent code changes.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
hqe
Comprehensive codebase health auditing, remediation, and verification skill based on the canonical HQE Protocol v5.0.0.
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…