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/tessro/fab/docs-reviewnpx skills add tessro/fab --skill docs-reviewgit clone --depth 1 https://github.com/tessro/fabWrote 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/tessro/fab/docs-review)<a href="https://agentmods.dev/skills/tessro/fab/docs-review"><img src="https://agentmods.dev/badge/skills/tessro/fab/docs-review.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.00030 | $0.00745 |
| Opus 5 | $0.00015 | $0.00373 |
| Sonnet 5 | $0.00006 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
docs-review 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 3d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Review
Assess whether your code changes are adequately documented. This skill identifies features, configuration, CLI commands, and other user-facing changes that may need documentation updates.
When to Use
Run /docs-review after completing /review and before committing, especially when your changes include:
- New features or functionality
- Changes to CLI commands or flags
- Configuration changes
- API modifications
- New entrypoints or user-facing behavior
How to Review
Use the Task tool to spawn a sub-agent for documentation review. This provides a fresh perspective focused specifically on documentation accuracy.
Step 1: Run the Sub-Agent Review
Use the Task tool with subagent_type: "general-purpose" and a prompt like:
Review all code changes (committed and uncommitted) between main and the current worktree for documentation impact. Run `git diff main` to see all changes.
Analyze the changes to identify:
1. **User-Facing Changes**: New or modified features, behaviors, or functionality that users interact with
2. **CLI/Entrypoint Changes**: New commands, flags, subcommands, or changes to existing ones
3. **Configuration Changes**: New config options, environment variables, or changes to existing settings
4. **API Changes**: New endpoints, changed request/response formats, or deprecations
For each identified change, check:
- Is there existing documentation that covers this? (README, docs/, inline help, etc.)
- Does the existing documentation accurately reflect the new behavior?
- Is the documentation discoverable where users would look for it?
Then examine any documentation changes in the diff:
- Do doc changes accurately describe the feature?
- Are there inconsistencies between code and docs?
- Is anything documented that doesn't match the implementation?
Report:
- **Gaps**: User-facing changes without adequate documentation
- **Outdated**: Existing docs that no longer match the code
- **Suggestions**: Specific documentation improvements (be concise, not exhaustive)
- **Assessment**: Overall documentation status (adequate / needs updates / critical gaps)
Be pragmatic: not every internal refactor needs docs. Focus on what users need to know.
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.
- 3d ago First seen · 83 lines · 30 tokens per session scan A abc00b1c4353
docs-review is a skill published in the GitHub repository tessro/fab (23 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 745 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-08-30.
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…