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/rafaelszago/doc-everything/doc-everything-initnpx skills add rafaelszago/doc-everything --skill doc-everything-initgit clone --depth 1 https://github.com/rafaelszago/doc-everythingWrote 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/rafaelszago/doc-everything/doc-everything-init)<a href="https://agentmods.dev/skills/rafaelszago/doc-everything/doc-everything-init"><img src="https://agentmods.dev/badge/skills/rafaelszago/doc-everything/doc-everything-init.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 | $0.00092 | $0.00769 |
| Opus 5 | $0.00046 | $0.00385 |
| Sonnet 5 | $0.00018 | $0.00154 |
| Haiku 4.5 | $0.00009 | $0.00077 |
Grade A, and why
doc-everything-init 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize doc-everything for this project
One-time setup so the docs-sync Stop hook and the document-feature-* skills
work in this repo. The hook works out of the box with sensible defaults — you
only need a config file if the defaults don't match this project's layout.
Steps
-
Inspect the repo layout. Find where source lives and what extensions are used (e.g.
src/,app/,lib/,packages/*, or a language-specific root), and where documentation should live. -
Decide if the defaults fit. The hook's built-in defaults watch common source roots (
src|app|lib|pkg|internal|cmd|packages) across many languages, exclude tests/vendored/generated code, and expect docs underdocs/features/. If that already matches this repo, skip the config file — less to maintain. -
Only if needed, write
.claude/doc-everything.jsonat the repo root with the keys that differ from the defaults:{ "docsPath": "docs/features/", "srcGlob": "(src|app)/[^[:space:]]+\\.(ts|tsx)", "srcExclude": "(\\.(test|spec)\\.|/__tests__/|/node_modules/)", "reason": "Source changed but nothing under {DOCS_PATH} did — document the feature." }srcGlob/srcExcludeare extended regexes matched againstgit status --porcelainlines. Escape backslashes for JSON (\\.).docsPathmust end with a trailing slash.reasonis optional;{DOCS_PATH}in it is substituted at runtime.- Any omitted key falls back to the built-in default.
- Alternatively, these map to env vars
DOC_EVERYTHING_SRC_GLOB,DOC_EVERYTHING_SRC_EXCLUDE,DOC_EVERYTHING_DOCS_PATH,DOC_EVERYTHING_REASON.
-
Scaffold the docs directory and index. Create the docs path if missing and seed
docs/features/README.md:# Features Per-feature documentation. Each feature has a `product.md` (user-facing view) and a `technical.md` (engineering view). | Feature | What it is | Docs | |---------|------------|------|
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 First seen · 69 lines · 92 tokens per session scan A fa9aa6b2d34a
doc-everything-init is a skill published in the GitHub repository rafaelszago/doc-everything (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 769 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…