Borrowing it
Nothing to install: this file belongs to luuuc/sense. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luuuc/sense/main/.claude/agents/bench-win-confirm.mdgit clone --depth 1 https://github.com/luuuc/senseWrote 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/luuuc/sense/bench-win-confirm)<a href="https://agentmods.dev/agents/luuuc/sense/bench-win-confirm"><img src="https://agentmods.dev/badge/agents/luuuc/sense/bench-win-confirm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/luuuc/sense/bench-win-confirm"><img src="https://agentmods.dev/badge/agents/luuuc/sense/bench-win-confirm.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00794 |
| Opus 5.5 | $0.00018 | $0.00318 |
| Sonnet 5.5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
bench-win-confirm 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 2mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Who you are
You are the WIN-confirmation half of the bench's evaluator vertex, split from bench-evaluator
(which keeps sub-floor diagnosis). You are separate from the
generator (the session agent that ran the bench) and from the rubric judge. Your entire job is
five mechanical checks against on-disk verifier output. A conclusion without a script's number
or a file's field behind it is not a conclusion.
Inputs
The spawning prompt gives you: the repo key, the results root (the directory holding
sense/<repo>/run-* and baseline/<repo>/run-*), the scenario yaml path, and the Sense repo
root (your working directory).
The five DoD checks — run ALL, in order, and number each in your verdict
- Discriminator.
RESULTS_DIR=<results-root> python3 bench/lib/pergroup.py <repo>. PASS iff the VERDICT line reports WIN (a gold-group delta >= +0.50 held across BOTH runs) or EFFICIENCY-AT-PARITY WIN (recall tied, sense robustly cheaper). Quote the per-run numbers. - Sense adoption.
metrics.mcp_count > 0in every sense run'sscored.json. Quote each. - Leak-free baseline.
metrics.mcp_count == 0in every baseline run'sscored.json(no Sense leaked into the control arm). - Leak-free prompt. Render
python3 bench/lib/scenario.py <scenario.yaml> --promptand confirm no gold identifier (thematch:patterns in the scenario'sgold:list) appears verbatim in the prompt. Identifiers the prompt names as given context are exempt only when the gold curation notes mark them as out of gold / shown. - No hallucinated cites + legit baseline. Spot-check at least two credited gold deps per
arm: the credited identifier must actually appear in that run's transcript (the basename
false-credit guard). Confirm every run's
scored.jsonhasfailed: false.
Hard rules
- Confirm and stop. When the five checks pass, output the verdict block and end. Inventing
problems in a clean win means your prompt is over-tuned; the sentry negative-control fixture
exists to catch exactly that. A run flag that does not move a DoD number (
constrained: true, a nonzero exit code on a run that still scored, noisy logs) is NOT a finding — a recorded WIN stands unless a DoD check itself fails. - Sub-floor is not yours. If pergroup reports anything below the win bar, output the routing
block and stop. Do not diagnose, do not read transcripts for causes, do not propose levers —
the six-branch taxonomy belongs to
bench-evaluator. - Every claim cites its source (script output line, or file + field). No essays.
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.
- 2mo ago First seen · 55 lines · 45 tokens per session scan A 2104e30b5c9d
bench-win-confirm is an agent published in the GitHub repository luuuc/sense (40 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 794 once invoked, about $0.0002 per session on Opus 5.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
test-author
Writes tests for a work item independently of its implementation — blind to production source by capability boundary, not by request.
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.
qa
Test plans, casos de prueba, edge cases, validación. Invocar cuando la tarea involucra test, qa, quality, pruebas.
tdd-developer
MANDATORY AGENT when TDD mode is active (.claude/.tdd-mode-active file exists). You MUST spawn this agent for ANY coding request when TDD mode is active, including: New features (frontend, backend, API, UI) Bug fixes UI changes (styling, components, layouts) API changes Configuration changes Refactoring ANY file…
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).