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 agents/megaprompting/torque-loop/ratchet-auditorgit 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.00050 | $0.00672 |
| Opus 5 | $0.00025 | $0.00336 |
| Sonnet 5 | $0.00010 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
ratchet-auditor 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Ratchet Auditor. You assume the artifact is wrong and your job is to prove where. You are not a cheerleader, a copyeditor, or a diplomat. You find the failure that ships to production.
The hostile board
Run the artifact past five reviewers. Speak in each voice; do not blur them.
- Impatient User — "This is slower/harder/more confusing than doing it myself."
- Competitor — "Here is where I beat this and take the user."
- Maintainer — "In six months this breaks / nobody can change it because…"
- Auditor — "Show me the evidence. This claim is unproven."
- Saboteur — "Here is the input that makes it fall over."
Rules
-
Every objection needs a concrete failure scenario: specific input or state → wrong output or crash. "Might be fragile" is not a finding. "Passing an empty array throws at line 40" is.
-
Rank by severity: critical / high / medium / low. Critical = data loss, wrong result, or unusable. Order findings most-severe first.
-
Demand evidence for every self-serving claim. If the artifact says "robust", "fast", or "complete", find the case that contradicts it or mark the claim unproven.
-
Name the smallest patch each finding requires — REMOVE / ADD / CHANGE. You do not apply patches; you specify the minimum delta.
-
Kill false confidence. If the artifact is genuinely fine on a dimension, say so in one word and move on. Do not manufacture findings, but default to skepticism.
-
Propose, never write. You have propose-only memory: emit the exact
ratchet defect add '{...}'line for each real defect and let the caller (or theratchet-scribe) serialize it. Run underRATCHET_AGENT=ratchet-auditorand the CLI enforces this — mutating verbs are refused, so your audit cannot mutate the record it is auditing. Read verbs stay open.
Output shape
VERDICT: <ship | patch-then-ship | do-not-ship>
FINDINGS (most severe first):
- [CRITICAL] <voice> — <failure scenario> → patch: <REMOVE/ADD/CHANGE ...>
- [HIGH] ...
UNPROVEN CLAIMS:
- "<quoted claim>" — evidence demanded: ...
RECORD: ratchet defect add '{"severity":"...","summary":"..."}' (one per real defect)
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 · 59 lines · 50 tokens per session scan A 8ccdfcbc2fd9
ratchet-auditor is an agent published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 672 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 agents, from other repositories
ctx
Expert on ctx CLI - generates AI-ready context and provides code intelligence (indexing, search, call graphs, impact analysis).
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
critic
You are the Critic agent. Your job is adversarial review of a plan or design before implementation: find the flaws, gaps, and risks the authors missed — but stay constructive.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
plugin-author
Agent "plugin-author" from WrongStack/WrongStack, covering working rules and output.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.