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-test-pipelinegit 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-test-pipeline)<a href="https://agentmods.dev/skills/bop-clocktower/canary/canary-test-pipeline"><img src="https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-test-pipeline/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-test-pipeline"><img src="https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-test-pipeline.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.00054 | $0.01354 |
| Opus 5 | $0.00027 | $0.00677 |
| Sonnet 5 | $0.00011 | $0.00271 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
canary-test-pipeline 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Canary: Test Pipeline
Runs the full test intelligence pipeline from risk assessment to verified CI
readiness. Follows the same pattern as harness:docs-pipeline and
harness:knowledge-pipeline — sequential phases, convergence loop, qualitative
health report on exit.
When to Use
-
Starting a new test suite from scratch
-
Improving a suite that is not yet CI-ready
-
After a major feature lands and test coverage needs updating
-
When asked to "bring this suite to CI-ready"
Phases
Phase 0 — Probe, then gate (/canary-ci-ready)
Probe for the harness MCP exactly once, here, and thread the result through
every later phase. Several sub-skills (canary-critical-areas,
canary-failure-impact, canary-ci-ready) each adapt to whether harness
primitives are available. Left alone they rediscover that independently, which
is wasted work and — worse — can yield an inconsistent run where one phase
scores against the graph and another silently falls back.
Record the probe result once:
harness: available → phases may call get_impact, get_critical_paths,
get_perf_baselines, ask_graph
harness: unavailable → every phase uses its documented fallback
Pass that verdict to each phase rather than letting it re-probe. If the probe is ambiguous, treat harness as unavailable — a consistent weaker run beats a run whose fidelity varies by phase, because a mixed run's health report cannot be compared against any previous one.
Then run canary-ci-ready as a baseline.
-
If CI-READY: inform the user and offer to exit or run an improvement sweep anyway.
-
If NOT CI-READY: show the score, continue to Phase 1.
Phase 1 — Assess (/canary-critical-areas)
Run canary-critical-areas on the repo (or --diff if provided). Save
critical-areas.json automatically (no --save required when run inside the
pipeline).
Present the top 5 areas and ask the user to confirm or trim the list before continuing.
Phase 2 — Discover (/canary-edge-cases)
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 · 160 lines · 54 tokens per session scan A 5aeb86332818
canary-test-pipeline is a skill published in the GitHub repository bop-clocktower/canary (4 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,354 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.