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 adamdroberts/agent-skills --skill deep-documentationgit clone --depth 1 https://github.com/adamdroberts/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/adamdroberts/agent-skills/deep-documentation)<a href="https://agentmods.dev/skills/adamdroberts/agent-skills/deep-documentation"><img src="https://agentmods.dev/badge/skills/adamdroberts/agent-skills/deep-documentation.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.00090 | $0.02484 |
| Opus 5 | $0.00045 | $0.01242 |
| Sonnet 5 | $0.00018 | $0.00497 |
| Haiku 4.5 | $0.00009 | $0.00248 |
Grade A, and why
deep-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 7d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Documentation
Use this skill when the task is to produce or maintain serious repository documentation, not a light README pass. The target quality bar is a repo where humans and LLMs can both understand how to use the system, what changed, and where to find the exact surface they need.
Documentation is part of delivery. If the code, API, setup, workflow, or behavior changes, the docs change in the same task.
Core rules
- Ground everything in the real repo. Read code, config, routes, schemas, tests, and existing docs before writing.
- Do not write vague marketing prose. Write operational, exact documentation.
- Keep the documentation layered: overview for orientation, guides for workflows, reference for exact interfaces, internals for maintainers.
- Use Mermaid diagrams in architectural documentation and anywhere business logic, workflow, or system behavior is easier to understand visually.
- Treat LLM-facing documentation as first-class project artifacts, not an afterthought.
- Treat changelog updates as required for meaningful changes.
- Create or update repo-local agent skills when the repo has distinct workflows or tool surfaces that future LLMs should follow.
Documentation standard
Documentation at this level should usually include most or all of these surfaces:
README.mdfor the current product story, setup, quickstart, and top-level links.docs/README.mdor equivalent index that maps the full documentation set.- Guide pages for how to build, use, run, or operate the system.
- Reference pages for public APIs, endpoints, tools, config fields, schema shapes, environment variables, and commands.
- Internal architecture or subsystem pages for maintainers.
- Testing or verification docs when the repo has a meaningful test surface.
- Agent-skills documentation when the project wants LLMs to use the codebase in a specific way.
llms.txtas the concise LLM index.llms-full.txtas the single-file documentation bundle for ingestion.CHANGELOG.mdas the append-only historical record.
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.
- 7d ago First seen · 288 lines · 90 tokens per session scan A 47dedade8466
deep-documentation is a skill published in the GitHub repository adamdroberts/agent-skills (9 stars, last pushed 4mo ago), licensed MIT. It adds 90 tokens to every session and 2,484 once invoked, about $0.0005 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-08-31.
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…