What is canary-watch?

A monitoring guide for checking a deployed website or application after a release, merge, or dependency update. It checks whether pages, APIs, browser behavior, content, and performance still work.

Use it for quick checks, repeated monitoring during a launch, or comparisons between staging and production URLs.

It helps catch production regressions that may not appear during local testing, such as broken API calls, missing page elements, console errors, or slower loading.

canary-watch — Skill for Claude Code by sifxprime

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 sifxprime/kodelyth-ecc --skill canary-watch

Clone the repo

git clone --depth 1 https://github.com/sifxprime/kodelyth-ecc

Made for: Claude Code.

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/sifxprime/kodelyth-ecc/canary-watch/github.svg)](https://agentmods.dev/skills/sifxprime/kodelyth-ecc/canary-watch)

Your own site

<a href="https://agentmods.dev/skills/sifxprime/kodelyth-ecc/canary-watch"><img src="https://agentmods.dev/badge/skills/sifxprime/kodelyth-ecc/canary-watch/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/sifxprime/kodelyth-ecc/canary-watch"><img src="https://agentmods.dev/badge/skills/sifxprime/kodelyth-ecc/canary-watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 675 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 84% copy Near-identical to another mod 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.00025	$0.00675
Opus 5	$0.00013	$0.00338
Sonnet 5	$0.00005	$0.00135
Haiku 4.5	$0.00003	$0.00068

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

Security

Grade A, and why

canary-watch 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.

Origin

This is a copy

84% identical to canary-watch — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/canary-watch/SKILL.md · 100 lines

How it starts

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

Canary Watch — Post-Deploy Monitoring

When to Use

After deploying to production or staging
After merging a risky PR
When you want to verify a fix actually fixed it
Continuous monitoring during a launch window
After dependency upgrades

How It Works

Monitors a deployed URL for regressions. Runs in a loop until stopped or until the watch window expires.

What It Watches

1. HTTP Status — is the page returning 200?
2. Console Errors — new errors that weren't there before?
3. Network Failures — failed API calls, 5xx responses?
4. Performance — LCP/CLS/INP regression vs baseline?
5. Content — did key elements disappear? (h1, nav, footer, CTA)
6. API Health — are critical endpoints responding within SLA?

Watch Modes

Quick check (default): single pass, report results

/canary-watch https://myapp.com

Sustained watch: check every N minutes for M hours

/canary-watch https://myapp.com --interval 5m --duration 2h

Diff mode: compare staging vs production

/canary-watch --compare https://staging.myapp.com https://myapp.com

Alert Thresholds

critical:  # immediate alert
  - HTTP status != 200
  - Console error count > 5 (new errors only)
  - LCP > 4s
  - API endpoint returns 5xx

warning:   # flag in report
  - LCP increased > 500ms from baseline
  - CLS > 0.1
  - New console warnings
  - Response time > 2x baseline

info:      # log only
  - Minor performance variance
  - New network requests (third-party scripts added?)

Notifications

When a critical threshold is crossed:

Desktop notification (macOS/Linux)
Optional: Slack/Discord webhook
Log to ~/.claude/canary-watch.log

Output

## Canary Report — myapp.com — 2026-03-23 03:15 PST

### Status: HEALTHY ✓

| Check | Result | Baseline | Delta |
|-------|--------|----------|-------|
| HTTP | 200 ✓ | 200 | — |
| Console errors | 0 ✓ | 0 | — |
| LCP | 1.8s ✓ | 1.6s | +200ms |
| CLS | 0.01 ✓ | 0.01 | — |
| API /health | 145ms ✓ | 120ms | +25ms |

### No regressions detected. Deploy is clean.

Read the full file on GitHub · 100 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.

6d ago First seen · 100 lines · 25 tokens per session scan A c00a9bcc1ba1

Subscribe to this mod's changes

canary-watch is a skill published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 675 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to canary-watch, differing in 36 lines, and is treated as a copy.

Claude Code Cloud Debugging DevOps and cloud ai-agents antigravity automation claude coding-assistant

atmos-introspection

Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help= scoped CLI help.

cloudposse/atmos · 37 tokens

atmos-schemas

JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.

cloudposse/atmos · 32 tokens

atmos-lint

Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings. Use when configuring, running, debugging, or documenting Terraform/OpenTofu linting in an Atmos project.

cloudposse/atmos · 64 tokens

canary-watch