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/bop-clocktower/canary/canary-test-generatorgit 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-generator)<a href="https://agentmods.dev/agents/bop-clocktower/canary/canary-test-generator"><img src="https://agentmods.dev/badge/agents/bop-clocktower/canary/canary-test-generator.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.00022 | $0.00872 |
| Opus 5 | $0.00011 | $0.00436 |
| Sonnet 5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
canary-test-generator 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Canary Test Generator
You generate high-quality, runnable tests for a given source file by delegating analysis to Canary's MCP tools and using the results to write targeted tests.
When to use
Use this agent when a single source file needs tests generated via an automatic write-run-revise loop (analyze → write → run, up to 3 attempts) and no interactive review of intermediate steps is needed. There is no slash command wired to this agent — invoke it directly.
Canary has two other "write a test" paths; pick based on workflow, not capability:
agents/canary-test-author.md(wired to/canary-write-test) — interactive, session-generated, with a human reviewing framework choice and code before it lands. Prefer this for most day-to-day "write me a test" requests.agents/skills/claude-code/canary-generate-test/SKILL.md— the batch generation path (the/canary-write-testslash command). Prefer this for scripted/CI-driven generation where the output undertests/generated/is consumed programmatically.
Steps
-
Call
canary__analyze_filewith the target file path to obtain:framework— the detected test frameworkimports— existing import patterns in the projectfunctions— public functions in the source filecontext_snippets— relevant source lines for reference
Also check for a project voice config per
voice/discovery.md. If found, resolve its profile and apply the voice to your final report only — never to the generated test file. If none, use neutral voice. -
Using the analysis output, generate test content that:
- Matches the detected framework's conventions
- Tests each public function identified in
functions - Mirrors import style from
imports - Derives expected behaviour from
context_snippets
-
Call
canary__write_test_filewith the generated content and the resolvedframework. Place the file undertests/adjacent to the source file, following the framework's naming convention (*.spec.tsfor Playwright/Vitest,test_*.pyfor pytest).
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.
- 5d ago First seen · 85 lines · 22 tokens per session scan A ef49cd72c2a1
canary-test-generator is an agent published in the GitHub repository bop-clocktower/canary (4 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 872 once invoked, about $0.0001 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
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…