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 didacrios/ai-coding-protocols --skill documentationgit clone --depth 1 https://github.com/didacrios/ai-coding-protocolsWrote 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/didacrios/ai-coding-protocols/documentation)<a href="https://agentmods.dev/skills/didacrios/ai-coding-protocols/documentation"><img src="https://agentmods.dev/badge/skills/didacrios/ai-coding-protocols/documentation/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/didacrios/ai-coding-protocols/documentation"><img src="https://agentmods.dev/badge/skills/didacrios/ai-coding-protocols/documentation.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.00059 | $0.00897 |
| Opus 5.5 | $0.00024 | $0.00359 |
| Sonnet 5.5 | $0.00012 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
documentation 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 21d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
High-Precision Documentation Protocol
A protocol for generating in-code comments and system documentation. Uses the Diátaxis framework for external docs and enforces "explain why, not what" for inline comments.
When to Activate
- Writing or updating in-code documentation (TSDoc, PHPDoc)
- Creating system documentation in a
/docs/folder - Generating READMEs, tutorials, or how-to guides
- Documenting APIs, schemas, or architectural decisions
Core Concepts
- Why, not what — documentation explains reasoning, not mechanics
- Diátaxis framework — four types of docs, each with a clear purpose
- Synchronized updates — docs update in the same step as the code change
- Source-verified — read the implementation before writing about it
Detailed Guidance
In-Code Documentation (The "Reference" Layer)
Follow the recursive principle: documentation must explain why, not what.
- TypeScript: Use TSDoc. Explicitly document generics, complex union types, and interface contracts found in the project.
- PHP: Use PHPDoc. Mandatory
@throwsfor all identified exceptions in the call chain. - Synchronization: Documentation must be updated in the same "Baby Step" as the code change.
System Documentation (The /docs/ Folder)
When generating files for the project's /docs/ directory, strictly apply the Diátaxis Framework:
A. Tutorials (Learning-oriented)
- Focus: "Learning by doing". Abstract complexity to guarantee a successful first run.
B. How-To Guides (Problem-oriented)
- Focus: "Solving a specific task". Steps for real-world goals (e.g., "Adding a new Payment Gateway").
C. Explanations (Understanding-oriented)
- Focus: "Concepts and Architecture". Discuss recursive dependencies, design patterns, and system constraints.
D. Reference (Information-oriented)
- Focus: "Technical facts". Exhaustive descriptions of APIs, schemas, and classes.
Recursive Context Check
Before writing any documentation:
- Source Trace: Read the actual implementation to ensure the documentation is technically accurate.
- Global Context: Search the
./docs/folder for existing guides to avoid duplication and maintain a consistent voice. - Link Verification: Ensure all file paths and cross-references between
./docs/and source code are valid.
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.
- 21d ago Changed · +1 lines · +41 tokens per session 2f9edc660f00
- 2mo ago First seen · 89 lines · 18 tokens per session scan A 5a425e2be4d0
documentation is a skill published in the GitHub repository didacrios/ai-coding-protocols (2 stars, last pushed 6d ago), licensed MIT. It adds 59 tokens to every session and 897 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…