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.
git clone --depth 1 https://github.com/EvoClaw/amplifyWrote 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/evoclaw/amplify/write-paper)<a href="https://agentmods.dev/commands/evoclaw/amplify/write-paper"><img src="https://agentmods.dev/badge/commands/evoclaw/amplify/write-paper/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/evoclaw/amplify/write-paper"><img src="https://agentmods.dev/badge/commands/evoclaw/amplify/write-paper.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00043 |
| Opus 5.5 | $0.00005 | $0.00017 |
| Sonnet 5.5 | $0.00003 | $0.00009 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
write-paper 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 1mo 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
Invoke the amplify:paper-writing skill and follow it exactly as presented to you
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.
- 1mo ago First seen · 7 lines · 13 tokens per session scan A 56d058801bf6
write-paper is a command published in the GitHub repository EvoClaw/amplify (11 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 43 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
read
Read a specific section from an arXiv paper's HTML version (ar5iv.org).
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
3-osp-historian
OSP Phase 3: Compress retrieved literature into a chronological domain narrative.
rclone_config_password
Update password in an existing remote.
rclone_test_changenotify
Log any change notify requests for the remote passed in.
uninstall
Uninstall filetree from this repo — un-wires CLAUDE.md/AGENTS.md, removes generated artifacts (confirmed per item), tears down self-only mode if enabled.