canary-migrator

canary-migrator is an agent for Claude Code from bop-clocktower/canary. It costs 28 tokens per session (301 once invoked), scanned A, original, MIT.

A migration assistant for moving a harness-scaffolded test project into Canary's layout. It first shows a dry-run plan, which lists intended changes without applying them.

In plain words
What is it for?
Use it to preview and, after explicit confirmation, apply a test-suite migration while reporting created files, skipped files, and follow-up tasks.
Why use it?
It lets you review which files will be created or preserved and what still needs manual work before anything is written.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

Good fit Use it to preview and, after explicit confirmation, apply a test-suite migration…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/bop-clocktower/canary/canary-migrator
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.

Clone the repo
git clone --depth 1 https://github.com/bop-clocktower/canary

Made for: Claude Code.

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

Wrote 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.

agentmods badge for canary-migrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/bop-clocktower/canary/canary-migrator.svg)](https://agentmods.dev/agents/bop-clocktower/canary/canary-migrator)
Your own site
<a href="https://agentmods.dev/agents/bop-clocktower/canary/canary-migrator"><img src="https://agentmods.dev/badge/agents/bop-clocktower/canary/canary-migrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00028 $0.00301
Opus 5 $0.00014 $0.00151
Sonnet 5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured 6d ago against content hash 7b769e01a39e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

canary-migrator 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 6d 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-migrator.md · 38 lines

What it actually says

Canary Migrator

You migrate a harness test-suite project to Canary's layout. Always show a dry-run plan before writing any files.

Steps

  1. Call canary__migrate with apply=false to produce a dry-run plan.

  2. Present the plan to the user:

    • files_created — files that will be written
    • files_skipped — existing files that will be preserved
    • manual_followups — actions the user must take after migration
  3. Ask the user to confirm: "Apply the migration? (yes/no)". Wait for an explicit "yes" before proceeding.

  4. On confirmation, call canary__migrate with apply=true.

  5. Report the actual files_created, files_skipped, and manual_followups from the response.

Constraints

  • Never call canary__migrate with apply=true without an explicit user confirmation in step 3.
  • If the dry-run response contains {"error": "no harness.config.json found"}, inform the user that the current directory is not a harness project and stop.
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. 6d ago First seen · 38 lines · 28 tokens per session scan A 7b769e01a39e

Subscribe to this mod's changes

canary-migrator is an agent published in the GitHub repository bop-clocktower/canary (4 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 301 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.