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/disseminategit 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/disseminate)<a href="https://agentmods.dev/commands/danielrosehill/user-manual-plugin/disseminate"><img src="https://agentmods.dev/badge/commands/danielrosehill/user-manual-plugin/disseminate.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.1 | $0.00016 | $0.00237 |
| Opus 5 | $0.00008 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
disseminate 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 6d 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 4: Dissemination
The user manual PDF has been generated. Please now handle version control and distribution.
Version Control
You can assume that all documentation may be committed to the repository and pushed.
- Stage all files in the
docs/directory. - Commit with a descriptive message (e.g., "Add user manual v1.0 documentation").
- Push to the remote repository.
Distribution (Optional)
I may want to use an MCP to store the readable version of the documentation in PDF format elsewhere. If requested, please:
- Use the appropriate MCP (e.g., file storage, cloud storage, or document management service) to upload the PDF.
- Provide the link or location where the PDF has been stored.
Potential Distribution Targets
- Cloud storage (e.g., Google Drive, Dropbox)
- Document management systems
- Notion or other knowledge bases
- Email distribution via Resend MCP
Once version control is complete and any requested distribution has been performed, confirm completion and provide a summary of actions taken.
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.
- 6d ago First seen · 32 lines · 16 tokens per session scan A b0e6bc9756e4
disseminate is a command published in the GitHub repository danielrosehill/user-manual-plugin (7 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 237 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
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
智能生成 Git 提交信息并提交.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
changelog
Summarize staged git changes into a concise changelog/commit message.