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/qa-ledgernpx skills add Megaprompting/torque-loop --skill qa-ledgergit 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.00067 | $0.00712 |
| Opus 5 | $0.00034 | $0.00356 |
| Sonnet 5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
qa-ledger 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ratchet:qa-ledger — the canonical quality ledger
Session state is "this session." The ledger is "everything we know about this codebase's quality surface." This command builds and maintains it. It is the memory that lets QA compound instead of restarting every session.
Step 0 — Ensure the ledger exists
ratchet ledger create
ratchet ledger get
Procedure
-
Features — from
/ratchet:repo-auditevidence (or discover now). Each feature is a row with a stable ID, area, the routes/workflows it covers, and a status (discovered→specced→covered→verified).ratchet ledger update features '{"name":"checkout","area":"commerce","routes":"/cart,/pay","status":"discovered"}' -
Tests — every test that exists or must exist, tied to a feature, with a kind (unit / integration / e2e / manual) and status (
pass/fail/missing).ratchet ledger update tests '{"feature":"<feature id>","name":"pay-with-expired-card","kind":"e2e","status":"missing"}' -
Defects — every known failure enters through the defect verbs, never through a generic ledger edit: the state defect family owns the mirror's status, severity, and summary end-to-end, so
ratchet defect addis the only birth door (it lands in the ledger automatically).ratchet defect add '{"feature":"<feature id>","severity":"high","summary":"..."}' -
Reconcile. Update statuses for anything that changed since last session — through the verbs that own each record. A test that now passes or a feature now covered reconciles with
ratchet ledger update tests|features ...; a defect reconciles only through its lifecycle:ratchet defect resolve <id> --evidence "<proof it is actually fixed>" ratchet defect reopen <id> --reason "<why it is not actually fixed>" ratchet defect supersede <id> --by <newId>
Rules
- Every feature must have evidence and at least one intended test. A feature with no test row is itself a defect — record the gap.
- Never mark a feature
verifiedwithout a passing test to point to. - Use stable IDs so updates upsert instead of duplicating.
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 · 73 lines · 67 tokens per session scan A 95e46087c1f8
qa-ledger is a skill published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 712 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.