What is canary-fleet-health?

A test-health summary for an entire collection of test suites, using past test runs to find flaky tests, sudden failure increases, shared failures, and possible regressions.

Use it for regular health checks, before releases, or when looking for regression and failure patterns across many suites.

It shows where test-maintenance effort may be needed before investigating individual tests. A flaky test is one that passes and fails without a relevant code change.

canary-fleet-health — Skill for Claude Code by bop-clocktower

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.

Any agent

npx skills add bop-clocktower/canary --skill canary-fleet-health

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 23 skills, 13 commands, 8 agents, 4 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-fleet-health/github.svg)](https://agentmods.dev/skills/bop-clocktower/canary/canary-fleet-health)

Your own site

<a href="https://agentmods.dev/skills/bop-clocktower/canary/canary-fleet-health"><img src="https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-fleet-health/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bop-clocktower/canary/canary-fleet-health"><img src="https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-fleet-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,428 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.

Model	Per session	Once invoked
Fable 5.1	$0.00117	$0.02428
Opus 5	$0.00059	$0.01214
Sonnet 5	$0.00023	$0.00486
Haiku 4.5	$0.00012	$0.00243

Measured 12d ago against content hash 200640b5b3ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

canary-fleet-health 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 12d 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/skills/claude-code/canary-fleet-health/SKILL.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Canary: Fleet Health

Wraps canary analyze (fleet-wide flake/spike/regression analytics) and the run-history store to answer "how's the whole fleet doing?" in one chat-turn summary. Today, canary-flake-hunter only diagnoses a single test you already suspect is flaky — this skill is the fleet-wide counterpart: it tells you where to look before you reach for the hunter.

Per the adoption audit this skill implements (candidate #10), this is deliberately a low-cost validation step: a compact text summary a human can scan in one turn, not a dashboard or visual surface. If fleet-wide analytics prove valuable, a richer surface is a separate, larger investment — don't over-build this one.

When to Use

Weekly/periodic health check: "how's the test fleet looking?"
Before a release: "any regressions or spikes we should know about?"
Triaging where to spend test-maintenance effort across many suites
NOT for a single test you already know is flaky — use canary-flake-hunter to diagnose root cause and propose a fix
NOT for scoring one suite's CI readiness — use canary-ci-ready (coverage depth, assertion quality, runtime for one suite)
NOT a substitute for .canary/critical-areas.json risk ranking — use canary-critical-areas for code-level risk, this skill is history-data-level health

Process

Phase 1: RESOLVE THE STORE

Fleet analytics read from the run-history store, not from a live test run. Before running anything, confirm data exists:

canary history summary <suite> --runs 1

Configured store: CANARY_HISTORY_DB_URL env var (Supabase-backed) or falls back to the local NDJSON file at test-results/reports/history-v2.jsonl.
No local file and no CANARY_HISTORY_DB_URL: there is nothing to analyze yet. Say so plainly — "No run history found. Push results with canary history push after a CI run, or run canary history migrate if you have v1 history.jsonl data." Do not fabricate a health summary from nothing.

Read the full file on GitHub · 197 lines

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.

12d ago First seen · 197 lines · 117 tokens per session scan A 200640b5b3ba

Subscribe to this mod's changes

canary-fleet-health is a skill published in the GitHub repository bop-clocktower/canary (4 stars, last pushed yesterday), licensed MIT. It adds 117 tokens to every session and 2,428 once invoked, about $0.0006 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.

Analytics and metrics Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

canary-fleet-health