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/darellchua2/opencode-config-template/documentation-consistency-skillnpx skills add darellchua2/opencode-config-template --skill documentation-consistency-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/documentation-consistency-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/documentation-consistency-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/documentation-consistency-skill.svg" alt="Measured on agentmods" 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.00033 | $0.03869 |
| Opus 5 | $0.00016 | $0.01935 |
| Sonnet 5 | $0.00007 | $0.00774 |
| Haiku 4.5 | $0.00003 | $0.00387 |
Grade A, and why
documentation-consistency-skill 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 2d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I detect and repair documentation drift across the repository's markdown files:
- Cross-File Count Sync — Verify skill/agent counts match reality across setup.sh, setup.ps1, README.md, and AGENTS.md
- PLAN vs Reality Drift — Detect stale checkboxes, mismatched acceptance criteria, and outdated scope sections in PLAN*.md files
- Structural Integrity — Validate required sections exist in PLAN files, README tables, and AGENTS.md routing tables
- Orphan/Stale References — Find skill/agent names in documentation that don't exist on disk, and vice versa
When to use me
Use this skill when:
- After adding, removing, or renaming skills or subagents
- Before creating a PR to verify documentation is consistent
- After a long work session with many edits to documentation files
- When PLAN checkboxes may not reflect actual implementation state
- Periodically as a health check against documentation rot
Trigger phrases:
- "check documentation consistency"
- "audit docs"
- "verify doc consistency"
- "check for documentation drift"
- "consistency check"
- "validate documentation"
Related Skills
| Skill | Relationship |
|---|---|
documentation-sync-workflow-skill |
Sync handles add/remove workflows for new skills/agents. This skill handles ongoing drift detection. Use sync when adding a skill; use consistency when verifying everything is still aligned. |
plan-updater-skill |
Updater marks checkboxes after commits. This skill validates those marks are accurate and complete. |
plan-execution-skill |
Execution runs PLAN phases. This skill can verify documentation state after execution. |
verification-loop-skill |
Verification checks code vs requirements. This skill checks documentation vs code state. |
opencode-skills-maintainer-skill |
Maintainer audits skill content quality. This skill audits documentation accuracy across files. |
Validation Levels
| Level | Categories Checked | Use Case |
|---|---|---|
quick |
Cross-file counts only | Pre-commit check |
standard |
Counts + PLAN drift + orphans | After a work session |
thorough |
All 4 categories | Pre-PR, after bulk changes |
targeted |
Single PLAN file (all categories) | During plan execution |
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.
- 2d ago First seen · 457 lines · 33 tokens per session scan A f2c65b51c24d
documentation-consistency-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 33 tokens to every session and 3,869 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…