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.
git clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/chrono-meta/forge-harness/quench-challenger)<a href="https://agentmods.dev/agents/chrono-meta/forge-harness/quench-challenger"><img src="https://agentmods.dev/badge/agents/chrono-meta/forge-harness/quench-challenger.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00099 | $0.05163 |
| Opus 5 | $0.00049 | $0.02582 |
| Sonnet 5 | $0.00020 | $0.01033 |
| Haiku 4.5 | $0.00010 | $0.00516 |
Grade A, and why
quench-challenger 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 8d 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 — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invocation examples
Moved out of
description:on 2026-08-11. They were an unquoted multi-line block whoseuser:/assistant:lines parsed as new YAML keys, which broke the whole frontmatter — so the declaredtools:and themodel: opusHARD FLOOR below it never took effect. Measured in a live session agent list: this agent showed(Tools: All tools)and the fallback description, while siblings showed exactly what they declared. Keepdescription:to ONE quoted line.
quench-challenger — Dedicated Attack-Prescription Synthesis Agent
Context and Background
This agent repeatedly analyzes harness structure failure patterns. Even when a SKILL.md looks complete, real execution repeatedly reveals: Done When is missing so completion can never be declared; a core feature silently disappears when an external plugin is removed; a new user cannot find the trigger so the skill effectively does not exist.
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.
- 8d ago First seen · 412 lines · 99 tokens per session scan A 68db4f44c572
quench-challenger is an agent published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 5,163 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-30.
Other agents, from other repositories
branch-setup
PRFlow implement's Phase 1.4 branch-setup agent — resume pre-check and feature-branch creation.
issue-claim-auditor
PRFlow implement's Phase 1.6 audit agent — pre-checks the issue's claims against the codebase.
checklist-generator
PRFlow review-engine agent; use to enumerate every verifiable claim in a code diff as a JSON checklist.
deferral-drafter
PRFlow implement's Phase 4.0 agent — drafts follow-up issue bodies for deferred criteria.
ac-claim-verifier
PRFlow implement's Phase 3.4 claim verifier — checks shipped code against each acceptance criterion.
ac-evidence-verifier
PRFlow implement's Phase 3.4 evidence verifier — runs the in-env verification command per criterion.