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/megaprompting/torque-loop/evolvenpx skills add Megaprompting/torque-loop --skill evolvegit clone --depth 1 https://github.com/Megaprompting/torque-loopWhat 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.00097 | $0.01750 |
| Opus 5 | $0.00048 | $0.00875 |
| Sonnet 5 | $0.00019 | $0.00350 |
| Haiku 4.5 | $0.00010 | $0.00175 |
Grade A, and why
evolve 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ratchet Evolve
Mutate. Test. Keep the delta. Serialize the next edge.
You are running a bounded artifact evolution loop. Your job is not to brainstorm improvements and not to "make this better." Your job is to produce evidence-gated deltas: one target, one pressure, small mutations, a proof gate, and a durable record.
LOCK → SNAPSHOT → PRESSURE → MUTATE → JUDGE → APPLY → VERIFY → KEEP/REVERT/ASK → RECORD → NEXT EDGE
The hard constraint, always:
No proof → no keep.
No keep → no progress claim.
No state → no loop continuity.
Invocation
/ratchet:evolve <target> --goal "<improvement>" [--iterations 2] [--test "<cmd>"] [--mode code|prompt|docs|workflow|auto] [--write]
Parse from $ARGUMENTS: the target artifact, the --goal, --iterations (default 2),
an optional --test command, --mode (default auto), and --write (default false —
without it, propose patches but do not modify files). If the target or goal is missing, go
straight to ASK.
The deterministic helpers live in the ratchet-evolve CLI (call via Bash; fall back to
node "<plugin root>/bin/ratchet-evolve" if not on PATH). In Claude Code,
<plugin root> is $CLAUDE_PLUGIN_ROOT; in Codex local development, use this repo root
or the installed plugin path shown by codex plugin list --json.
The loop
1. LOCK
State, before any edit: the exact target, the desired delta, the proof that the delta worked, and the forbidden scope. Scope drift is the primary failure mode — name what you will not touch.
2. SNAPSHOT
Capture the baseline. No baseline = rewriting, not evolving.
ratchet-evolve snapshot <target> --goal "<goal>" --mode <mode>
Records path, hash, git state, mode, byte/line count. Read the file for real before mutating.
3. PRESSURE
Choose one primary pressure and at most one secondary. Name the pressure you
reject and why (usually novelty, because it tempts a rewrite instead of a stronger
delta). ratchet-evolve pressure <mode> suggests a starting vector.
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 · 170 lines · 97 tokens per session scan A 6d22cdc2b82b
evolve is a skill published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,750 once invoked, about $0.0005 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 skills, from other repositories
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
factory-line
Factory line for executing one station of a declared multi-station program — read the installed line bundle (har line status), plan parallel work into isolated HAR slots, run the cumulative gate with har line gate, and hand off for human review. Use when asked to "run a factory line", "run the next station", "execute…
v1-milestone
Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
golden-rss
Use when testing the rss golden build.