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/statusnpx skills add Megaprompting/torque-loop --skill statusgit 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.00062 | $0.00476 |
| Opus 5 | $0.00031 | $0.00238 |
| Sonnet 5 | $0.00012 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
status 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.
What it actually says
/ratchet:status — read the ratchet
Orientation without re-derivation. This command reads durable state and tells you exactly where the ratchet sits, so you resume instead of restart.
Procedure
Lead with the receipt — one stable read that answers what is true, what changed, what is safe, what is blocked, and what happens next without transcript archaeology:
ratchet receipt
The receipt always shows the same eight sections in the same order — target · delta · proof · seam · verdict · authority · state · next — so a cold human or agent can resume in under a minute. Emptiness is stated, never omitted.
For the detailed state view or a specific read, add:
ratchet status # the full state summary
ratchet score confidence
ratchet snapshot repo
What you get
- Current objective — the locked target.
- Bottleneck — the chosen blocker.
- Confidence — three scoped layers (artifact · session · ledger health), so a verified patch is never shown as blocked because of unrelated debt.
- Active / last artifact — what exists now.
- Last decision — the most recent commitment.
- Open defects — unresolved failures, by severity.
- Open loops & untested assumptions — outstanding pressure.
- Next action + next command — where to go.
- Staleness warning — ⚠️ if work changed since the last
/ratchet:compile.
Output contract
Return the rendered receipt verbatim, then one line of interpretation:
READ: <one sentence — where the ratchet is and the single most useful next move>
If state is empty (no objective), say so and point to /ratchet:lock or /ratchet:ignite.
If stale, the honest next move is /ratchet:compile before anything else.
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 · 55 lines · 62 tokens per session scan A f6d512e872ec
status is a skill published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 476 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.