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/patchnpx skills add Megaprompting/torque-loop --skill patchgit 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.00054 | $0.00551 |
| Opus 5 | $0.00027 | $0.00275 |
| Sonnet 5 | $0.00011 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
patch 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ratchet:patch — minimal delta
The temptation after criticism is to rewrite. Rewriting throws away working parts and introduces new defects. This command patches the specific failures and nothing else.
Step 0 — Load state and open defects
ratchet status
ratchet state get defects
Procedure
-
Take the defect list as the work order. Only defects found by
/ratchet:attack(or recorded in state) are in scope. If you feel the urge to change something not on the list, stop — that is scope creep, not a patch. -
Express each fix as a minimal delta:
- REMOVE: what to delete.
- ADD: what to introduce.
- CHANGE: what to alter, from → to.
-
Preserve everything that passed. Working parts are untouched. Prefer the smallest diff that clears the defect over the "cleaner" larger one.
-
Retest the patched path. Run the specific 5-point test items the defect touched. Report the actual result — if a fix didn't hold, say so; do not claim green on faith.
-
Update defect status. Resolved defects get marked; anything still failing stays open and honest.
Output contract
PATCH (per defect):
- <defect> → REMOVE: ... | ADD: ... | CHANGE: ...
PATCHED ARTIFACT: <the changed artifact or diff>
RETEST: <which checks were re-run + pass/fail>
REMAINING DEFECTS: <still-open items, or "none">
Serialize
Clear the ORIGINAL defect with the proof that it is fixed. Do not record a second, already-resolved defect: a defect cannot be born terminal (the CLI refuses it), and a freshly-minted "resolved" record leaves the real one draining forever.
ratchet defect resolve <original-defect-id> --evidence "<the retest result that proves it>"
ratchet state set phase patch
ratchet score confidence
Anything still failing stays open and honest — ratchet defect list shows what drains.
Next: if defects remain critical/high, loop back to /ratchet:attack. If clear,
/ratchet:compile to serialize the advance.
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.
- 2d ago First seen · 64 lines · 54 tokens per session scan A 9f4f5e3ff20e
patch is a skill published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 551 once invoked, about $0.0003 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.