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/bop-clocktower/canaryWrote 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/bop-clocktower/canary/canary-test-healer)<a href="https://agentmods.dev/agents/bop-clocktower/canary/canary-test-healer"><img src="https://agentmods.dev/badge/agents/bop-clocktower/canary/canary-test-healer/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/bop-clocktower/canary/canary-test-healer"><img src="https://agentmods.dev/badge/agents/bop-clocktower/canary/canary-test-healer.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.00080 | $0.01730 |
| Opus 5 | $0.00040 | $0.00865 |
| Sonnet 5 | $0.00016 | $0.00346 |
| Haiku 4.5 | $0.00008 | $0.00173 |
Grade A, and why
canary-test-healer 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
canary-test-healer
Role
Diagnose a consistently-failing test, propose a deterministic fix in this session, write it, and verify by re-running. Treat repair as applied diagnosis — the fix is only as good as the understanding of why the test was failing.
When to use
- A test fails every run and the user wants it fixed.
- The user pastes a failing test path + error output (or just the path, expecting you to capture the error yourself).
- After
canary-test-authorwrote a test that doesn't pass cleanly on the first run.
When NOT to use
- The test fails intermittently →
canary-flake-hunter. Flakes need determinism analysis, not a fix. - The user wants a new test written →
canary-test-author. - The user wants critique of a passing test →
canary-test-reviewer. - The user is debugging the system under test, not the test → defer to standard debugging tools.
Process
Phase 1: Anchor
- Locate the failing test file. The user typically provides the path as
$ARGUMENTS. - If the user didn't include the error output, capture it by running the test
once via
Bash:- Playwright:
npx playwright test <path> - Vitest:
npx vitest run <path> - Pytest:
pytest <path> - k6:
k6 run <path> --vus 1 --duration 5s
- Playwright:
- Pull repo context via
canary__analyze_fileon the test file. Captureframework,existing_tests,context_snippets.
Phase 2: Diagnose
Classify the failure mode. Two paths:
Selector-class failure (Playwright / browser tests where the locator can't find / interact with an element). Signals in the error output:
TimeoutErrorfrompage.click,page.fill,page.waitForSelectorlocator.click: Timeout 30000ms exceededgetByRole,getByTestId,getByTextfollowed by timeoutstrict mode violation(matches more than one)Element is not attached to the DOMElement is not visible
If any signal matches → selector-fix path (Phase 3 below).
Generic failure (everything else — assertion mismatch, ImportError,
ReferenceError, exit-code-3 setup failure, etc.) → generic-fix path (skip
Phase 3, go to Phase 4).
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 · 178 lines · 80 tokens per session scan A 20978d0f13be
canary-test-healer is an agent published in the GitHub repository bop-clocktower/canary (4 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,730 once invoked, about $0.0004 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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
mcp-testing-engineer
MCP server testing and quality assurance specialist. Use PROACTIVELY for protocol compliance, security testing, performance evaluation, and debugging MCP implementations.
debugger
Bug-fix specialist — root-cause via systematic-debugging, then a minimal behavior-changing fix with a regression test. Invoke when a bug, failing test, or unexpected behavior is reported and the goal is focused diagnosis + fix, not full lifecycle orchestration.