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 skills/ruvnet/metaharness/plan-changenpx skills add ruvnet/metaharness --skill plan-changegit clone --depth 1 https://github.com/ruvnet/metaharnessWrote 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/skills/ruvnet/metaharness/plan-change)<a href="https://agentmods.dev/skills/ruvnet/metaharness/plan-change"><img src="https://agentmods.dev/badge/skills/ruvnet/metaharness/plan-change.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.00019 | $0.00101 |
| Opus 5 | $0.00010 | $0.00051 |
| Sonnet 5 | $0.00004 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
plan-change 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.
This is a copy
100% identical to plan-change — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
plan-change
Produce an implementation plan for a requested change.
- Restate the goal in one sentence.
- List the files to touch and why.
- Name the smallest interface that satisfies it.
- Flag anything that ripples beyond three files or widens a permission.
Hand the plan to the implementer; do not write code in this step.
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 · 16 lines · 19 tokens per session scan A 84e1c44ca264
plan-change is a skill published in the GitHub repository ruvnet/metaharness (630 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 101 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to plan-change, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-agent
Agent skill for agent - invoke with $agent-agent.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-performance-benchmarker
Agent skill for performance-benchmarker - invoke with $agent-performance-benchmarker.
agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager.
agent-topology-optimizer
Agent skill for topology-optimizer - invoke with $agent-topology-optimizer.
agent-benchmark-suite
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite.