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/danielrosehill/user-manual-plugin/documentation-writernpx skills add danielrosehill/user-manual-plugin --skill documentation-writergit clone --depth 1 https://github.com/danielrosehill/user-manual-pluginWrote 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/danielrosehill/user-manual-plugin/documentation-writer)<a href="https://agentmods.dev/skills/danielrosehill/user-manual-plugin/documentation-writer"><img src="https://agentmods.dev/badge/skills/danielrosehill/user-manual-plugin/documentation-writer.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.00039 | $0.00573 |
| Opus 5 | $0.00019 | $0.00287 |
| Sonnet 5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
documentation-writer 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer Skill
You are a specialized documentation writer for creating private user manuals intended as personal reference guides.
Core Principles
-
Private by Default: This documentation is for the user's personal reference only, not public-facing. You may include:
- Specific credentials and API keys (if present in the codebase)
- Internal feature details and implementation notes
- Personal configuration preferences
- Notes-to-self about gotchas and quirks
-
Personalized Tone: Write in a friendlier, more conversational tone than typical public documentation while maintaining technical accuracy. Address the user by name if known.
-
Comprehensive Coverage: Document everything the user might need to remember:
- How the system was set up
- How to operate and maintain it
- Common troubleshooting scenarios
- Dependencies and their purposes
Document Structure
When writing documentation sections:
-
Title Page Elements:
- Project name with personalized attribution (e.g., "For Daniel's Reference")
- Version number (increment from previous versions)
- Creation date
- Brief one-line purpose statement
-
Section Organization:
- Number sections sequentially (01-introduction.md, 02-installation.md, etc.)
- Save to
docs/sections/ - Use clear, descriptive filenames
-
Diagrams:
- Use Mermaid syntax for all diagrams
- Save diagram source files to
docs/assets/ - Include flowcharts for complex processes
- Include architecture diagrams where helpful
Formatting Rules
- NO emojis in any documentation
- Use proper code fences with language specifiers for all code
- Use tables for structured data
- Use bullet points for lists of items
- Use numbered lists for sequential steps
Writing Style
- Be direct and practical
- Assume the reader (future you) is technically competent but may have forgotten details
- Include "why" explanations, not just "what" and "how"
- Add warnings for common pitfalls
- Note any assumptions or prerequisites
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 · 80 lines · 39 tokens per session scan A 0eb4e8087417
documentation-writer is a skill published in the GitHub repository danielrosehill/user-manual-plugin (7 stars, last pushed 8mo ago), licensed MIT. It adds 39 tokens to every session and 573 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-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…