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 skills add bop-clocktower/canary --skill canary-ci-readygit 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/skills/bop-clocktower/canary/canary-ci-ready)<a href="https://agentmods.dev/skills/bop-clocktower/canary/canary-ci-ready"><img src="https://agentmods.dev/badge/skills/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/skills/bop-clocktower/canary/canary-ci-ready"><img src="https://agentmods.dev/badge/skills/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.00064 | $0.01327 |
| Opus 5 | $0.00032 | $0.00664 |
| Sonnet 5 | $0.00013 | $0.00265 |
| Haiku 4.5 | $0.00006 | $0.00133 |
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 10d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Canary: CI Ready
Analyses a test suite across five dimensions and produces a readiness score. Use
this before promoting a suite to CI, or as the convergence gate in
/canary-test-pipeline.
When to Use
-
Before wiring a new test suite into CI for the first time
-
When a CI run is failing and you need to understand why
-
As part of
/canary-test-pipeline(Phase 0 and convergence gate) -
When asked "is this suite ready for CI?"
The Five Checks
Run all five checks and score each pass / warn / fail.
1. Coverage depth
Read .canary/test-inventory.json if present. If absent or older than 7 days,
run canary coverage to generate fresh data.
Default threshold: depth ≥ 2 for all endpoints in critical areas. Override with
--threshold <n>.
-
pass — all critical-area endpoints at depth ≥ threshold
-
warn — some endpoints at depth 1 (hit but unasserted)
-
fail — any critical-area endpoint at depth 0
2. Flakiness
Read test-results/quarantine-ledger.json (or the path in
.canary/company.json under quarantine_ledger_path if set).
A quarantined test is acceptable only when it has a linked open issue (Jira or GitHub). Check issue state:
-
Linked issue open → counts as verified (documented, tracked)
-
Linked issue closed → flag: quarantine should be resolved
-
No linked issue → fail: unlinked quarantine blocks CI-ready
3. Assertion quality
Read depth scores from the inventory. In critical-area endpoints:
-
pass — all tests at depth ≥ 2 (shaped assertions: result.ok or equivalent)
-
warn — some tests at depth 1 (status-only assertions)
-
fail — majority of critical-path tests at depth 1
4. Critical path coverage
Only run this check if .canary/critical-areas.json is present.
Cross-reference the top 5 risk-scored areas from critical-areas.json against
test-inventory.json:
-
pass — all top-5 areas have at least one test at depth ≥ 1
-
warn — one area uncovered
-
fail — two or more top areas uncovered
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 162 lines · 64 tokens per session scan A ec3691ae40bc
canary-ci-ready is a skill published in the GitHub repository bop-clocktower/canary (4 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,327 once invoked, about $0.0003 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 skills, from other repositories
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.