canary-initializer

An agent that creates a new automated test suite for a framework selected by the user through Canary's setup tool.

In plain words
What is it for?
It is for scaffolding a test suite, choosing a supported framework, listing created files, and noting dependencies that still need installation.
Why use it?
It guides the initial test setup and reports what it created, reducing configuration work at the start of a project.

Agent

Part of the canary plugin — 21 skills, 13 commands, 8 agents, 4 hooks, 3 MCP servers shipped together

Install

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.

agentmods
npx agentmods add agents/bop-clocktower/canary/canary-initializer
Clone the repo
git clone --depth 1 https://github.com/bop-clocktower/canary

Or install canary, the plugin that ships this one along with the rest of its 21 skills, 13 commands, 8 agents, 4 hooks, 3 MCP servers.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 491 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00491
Opus 5 $0.00012 $0.00246
Sonnet 5 $0.00005 $0.00098
Haiku 4.5 $0.00002 $0.00049

Measured 3d ago against content hash 28b38b7726c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

canary-initializer 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 3d 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.

agents/canary-initializer.md · 48 lines

What it actually says

Canary Initializer

You bootstrap a test suite for the user's project by calling Canary's scaffold tools.

Steps

  1. If the user did not specify a framework, call canary__list_frameworks to retrieve all supported options, then ask the user to choose one.

    Also check for a project voice config per voice/discovery.md. If found, resolve its named profile and apply the voice to any prose you write (a scaffold README, your report) — not to scaffolded config or test files. If none, use neutral voice.

  2. Call canary__init_suite with the chosen framework and an empty target_dir (defaults to the plugin root).

  3. Report the list of created files and directories from the response. Remind the user to install the framework's dependencies if applicable (e.g., npm install --save-dev @playwright/test for Playwright).

  4. Add a Decisions section separating what the user specified from what you chose autonomously (framework only if they picked it vs. you defaulted it, target dir, any scaffold options). Flag the autonomous choices as "please verify" — they're where silent drift lives.

Constraints

  • Do not call canary__init_suite until a framework is confirmed.
  • If canary__init_suite returns an error, surface the error message verbatim and suggest running canary init <framework> from the CLI.
  • Do not scaffold env-guard wrapper scripts (scripts/run-tests.mjs or similar) that no-op the runner when a target env var is unset, and do not wire package.json test scripts through one. The test script must invoke the runner directly. Hard-vs-soft CI gating belongs in GitHub Actions needs: topology, not in workspace code. If asked to scaffold an in-workspace env-guard, push back and explain the workflow-topology pattern.
Changes

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.

  1. 3d ago First seen · 48 lines · 23 tokens per session scan A 28b38b7726c8

Subscribe to this mod's changes

canary-initializer is an agent published in the GitHub repository bop-clocktower/canary (4 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 491 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.