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/evoclaw/amplify/design-experimentgit 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/design-experiment)<a href="https://agentmods.dev/commands/evoclaw/amplify/design-experiment"><img src="https://agentmods.dev/badge/commands/evoclaw/amplify/design-experiment.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.00011 | $0.00042 |
| Opus 5 | $0.00005 | $0.00021 |
| Sonnet 5 | $0.00002 | $0.00008 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
design-experiment 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.
What it actually says
Invoke the amplify:method-framework-design 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.
- 4d ago First seen · 7 lines · 11 tokens per session scan A a14ff9cac361
design-experiment is a command published in the GitHub repository EvoClaw/amplify (12 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 42 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-30.
Other commands, from other repositories
profile
Save, apply, and share multi-agent configuration profiles.
rollback
Restore a skill to its previous version. Requires a history entry — created automatically when you use rolecraft update or re-install over an existing skill.
remove
Command "remove" from rolecraft-sh/rolecraft, covering rolecraft remove, usage, options, description and examples.
verify
Check installed skill integrity via content hash.
init
Generate FILETREE.md from scratch. Confirms overwrite if it already exists. --self-only keeps every artifact out of git.
audit
Diff live infrastructure against the spec and report drift by component name.