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/doc-setupgit clone --depth 1 https://github.com/danielrosehill/user-manual-pluginWhat 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.00017 | $0.00260 |
| Opus 5 | $0.00009 | $0.00130 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
doc-setup 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 2d 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.
What it actually says
Task 1: Documentation Repository Setup
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.
Context
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.
Setup Instructions
To begin creating the user manual, please proceed as follows:
- Create a
docsfolder within this repository. - Within the
docsfolder, create the following subdirectories:sections/- for individual documentation sectionsassets/- for diagrams and other assetsoutput/- for the final compiled documentation
- If there are previous iterations of user manual documentation visible, note the highest version number for use in subsequent tasks.
Once the folder structure is in place, confirm completion and await the next task instruction.
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.
- 2d ago First seen · 29 lines · 17 tokens per session scan A 294c72ea040d
doc-setup is a command published in the GitHub repository danielrosehill/user-manual-plugin (7 stars, last pushed 8mo ago), licensed MIT. It adds 17 tokens to every session and 260 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.