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/commands/bop-clocktower/canary/canary-ci-ready)<a href="https://agentmods.dev/commands/bop-clocktower/canary/canary-ci-ready"><img src="https://agentmods.dev/badge/commands/bop-clocktower/canary/canary-ci-ready/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/commands/bop-clocktower/canary/canary-ci-ready"><img src="https://agentmods.dev/badge/commands/bop-clocktower/canary/canary-ci-ready.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.00025 | $0.00081 |
| Opus 5 | $0.00013 | $0.00041 |
| Sonnet 5 | $0.00005 | $0.00016 |
| Haiku 4.5 | $0.00003 | $0.00008 |
Grade A, and why
canary-ci-ready 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 9d 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.
What it actually says
canary-ci-ready
Use the canary-ci-ready agent to analyse this test suite for CI readiness.
$ARGUMENTS
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.
- 9d ago First seen · 12 lines · 25 tokens per session scan A 8b7470feb4cb
canary-ci-ready is a command published in the GitHub repository bop-clocktower/canary (4 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 81 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 commands, from other repositories
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
ship
Mechanical pre-deploy gate — tests, build, tree state.
coverage-diff
Run the local diff-coverage check that mirrors CI's Diff coverage required gate.
harness:cicd-fleet
Autonomous CI/CD-remediation orchestrator — triage the red CI/CD-run and flaky-test backlog by cause, fan out worktree-isolated subagents that run the real deflake/heal pipeline, independently verify each fix by artifact and deterministic all-OS CI, and hand back a batch of remediation PRs for one bulk human review.…
ship
Before merging or deploying, run ALL of the following checks. Every gate must pass.
test-setup
Scaffold test framework and CI pipeline.