canary-instrument

canary-instrument is a skill for Claude Code from bop-clocktower/canary. It costs 77 tokens per session (1,394 once invoked), scanned A, original, MIT.

A Playwright test instrumentation setup that records which outgoing web requests each test made. Playwright is a tool for automating and testing web browsers, while OpenTelemetry supplies the tracing records that connect tests to requests.

In plain words
What is it for?
Use it to investigate request behavior in Playwright runs, such as finding which test sent a particular HTTP request.
Why use it?
It removes the need to track request ownership manually when several browser tests call external services. The result is a run.json file showing those relationships.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the canary plugin — 23 skills, 13 commands, 8 agents, 4 hooks shipped together

Good fit Use it to investigate request behavior in Playwright runs, such as finding which test sent a particular HTTP request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bop-clocktower/canary/canary-instrument
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-instrument
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.

agentmods badge for canary-instrument

README.md
[![agentmods](https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-instrument/github.svg)](https://agentmods.dev/skills/bop-clocktower/canary/canary-instrument)
Your own site
<a href="https://agentmods.dev/skills/bop-clocktower/canary/canary-instrument"><img src="https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-instrument/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.

agentmods 80×15 button for canary-instrument

Your own site · 80×15
<a href="https://agentmods.dev/skills/bop-clocktower/canary/canary-instrument"><img src="https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-instrument.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,394 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.01394
Opus 5 $0.00039 $0.00697
Sonnet 5 $0.00015 $0.00279
Haiku 4.5 $0.00008 $0.00139

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

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/cli.mjs, scripts/otel_bootstrap/instrument.mjs, scripts/otel_bootstrap/playwright-fixture.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-instrument/SKILL.md · 158 lines

How it starts

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

Canary Instrument

Correlate every outbound HTTP request in a Playwright run to the test that made it, using OTel span parent/child relationships. Zero required external dependencies to produce output — default file-based span export, no OTel collector needed.

Setup (two manual steps, once per suite)

This skill ships fixture files you wire into your own suite — it does not vendor OTel as a dependency of the canary package itself. Install these first:

npm install --save-dev \
  @opentelemetry/sdk-node @opentelemetry/api \
  @opentelemetry/auto-instrumentations-node \
  @opentelemetry/exporter-trace-otlp-http

1. Bootstrap the OTel SDK before Playwright starts — add NODE_OPTIONS to your test command (or playwright.config.ts's webServer/CI step):

NODE_OPTIONS="--import ./node_modules/canary/agents/skills/claude-code/canary-instrument/scripts/otel_bootstrap/instrument.mjs" \
  npx playwright test

Copy otel_bootstrap/instrument.mjs into your repo (e.g. otel/instrument.mjs) if you'd rather not reference the path inside node_modules.

2. Merge the root-span fixture into your fixtures.ts:

import { test as base } from '@playwright/test';
import { withTestSpan } from './otel_bootstrap/playwright-fixture';

export const test = withTestSpan(base);

Every test using this test export now opens a root span carrying test.id/test.title/test.file, and every HTTP call the test makes nests under it automatically — no manual span code in individual tests.

Invocation

canary skills run canary-instrument -- \
  --spans test-results/trace --output test-results \
  [--suite-type e2e_ui]

# Usage and options (exits 0; --spans/--output are not required for --help):
canary skills run canary-instrument -- --help

An unknown flag, a missing required flag, and a value-flag left without its value are all usage errors (exit 2). --help short-circuits ahead of the required-argument check, so it never complains about --spans/--output.

Read the full file on GitHub · 158 lines

Files

What ships with it

5 files 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.

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.

  1. 10d ago First seen · 158 lines · 77 tokens per session scan A aa4f3e179ff0

Subscribe to this mod's changes

canary-instrument is a skill published in the GitHub repository bop-clocktower/canary (4 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,394 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

browse

Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).

garrytan/gstack · 32 tokens

playwright-cli

A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.

UnicomAI/wanwu · 76 tokens

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

anthropics/skills · 35 tokens

create-verification-skill

Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".

get-bb/bb · 57 tokens

browser-qa

A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.

hashgraph-online/awesome-codex-plugins · 58 tokens

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog-foss · 112 tokens