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 commands/danielrosehill/user-manual-plugin/user-manualgit 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/commands/danielrosehill/user-manual-plugin/user-manual)<a href="https://agentmods.dev/commands/danielrosehill/user-manual-plugin/user-manual"><img src="https://agentmods.dev/badge/commands/danielrosehill/user-manual-plugin/user-manual.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.00014 | $0.00565 |
| Opus 5 | $0.00007 | $0.00282 |
| Sonnet 5 | $0.00003 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
user-manual 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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I would like to create a user manual to document what we created today and ensure I remember how to operate this codebase in the future.
Please note that the intended use of this user manual is strictly for my own private reference. This is not intended as public documentation.
In the unlikely event that this repository also contains a public-facing document, please create these private documents in a separate path that is .gitignored.
In most cases, however, there will not be any public-facing documentation created within a private repository.
The instructions provided to the documentation generation subagent should explain why this distinction and context are being provided: Private documentation may contain feature outlines, specific code snippets, or credentials that would otherwise never be included in public documentation.
Formatting And Tone Of Voice Guidelines
Relative to public-facing documentation, the documentation can be written in a friendlier tone of voice while still adhering to best standards of technical documentation writing.
Assuming you know my name, you can include it in the documentation, such as "Homebox Backup Script Operation User Manual for Daniel's Attention," and reference the date of creation.
Other document authoring rules:
- Do not use emojis
- Provide code samples in proper codefences
- Add diagrams where appropriate and valuable. Use Mermaid if possible. You can install the CLI on the host or use an MCP.
Also, include a version number. If there are previous iterations of the user manual visible, please use the next sequential version number for this creation.
Make sure to include a footer displaying the current page number and the total page count. Use IBM Sans as the font. If it is not available or installed, you can install it into this repository or, ideally, onto the host system.
Creation Procedure
To create the user manual, please proceed as follows:
- Create a
docsfolder. - Engage a documentation writing agent.
- Instruct the documentation authoring agent on the nature of this documentation creation project. Make the agent aware that the documentation should be written in a suitable tone of voice for my own reference.
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.
- 5d ago First seen · 48 lines · 14 tokens per session scan A 084cea4fe8e1
user-manual is a command published in the GitHub repository danielrosehill/user-manual-plugin (7 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 565 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.