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/howells/arc/refactorgit clone --depth 1 https://github.com/howells/arcWhat 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.00012 | $0.00028 |
| Opus 5 | $0.00006 | $0.00014 |
| Sonnet 5 | $0.00002 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
refactor 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 yesterday.
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 refactor skill with any arguments provided.
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.
- yesterday First seen · 7 lines · 12 tokens per session scan A f3afaf39262a
refactor is a command published in the GitHub repository howells/arc (25 stars, last pushed 17d ago), licensed MIT. It adds 12 tokens to every session and 28 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
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
verification-repair
PitWay: Bounded, approve-before-edit correction after every task is done.
task-discard
PitWay: Abandon a dispatched task's worktree without integrating.
milestone-status
PitWay: Show a milestone's status, contract, progress, and tasks.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
milestone-list
PitWay: List every milestone with a concise one-line status.