agentmods.dev

canary-setup-harness

canary-setup-harness is a skill for Claude Code from bop-clocktower/canary. It costs 133 tokens per session (2,261 once invoked), scanned A, original, MIT.

A setup procedure for adding Canary’s Harness Engineering checks to a new project or fork. It installs the command-line tool, creates its configuration, adds five continuous-integration workflows, and checks a clean repository.

In plain words
What is it for?
Use it when configuring Canary in a new repository or bringing a fork back in line with the expected setup.
Why use it?
It removes the manual work of connecting the project’s required checks and security record. It also catches setup problems before normal development begins.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/security_ledger.py.

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

not rated 4repo today A scan 133 tokens original MIT

Good fit Use it when configuring Canary in a new repository or bringing a fork back in line with the expected setup.

Compare 6 skills from other repositories ↓
View source ↗ bop-clocktower/canary
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/bop-clocktower/canary
agentmods
npx agentmods add skills/bop-clocktower/canary/canary-setup-harness

Made for: Claude Code.

Or install canary, the plugin that ships this one along with the rest of its 22 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-setup-harness

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/bop-clocktower/canary/canary-setup-harness"><img src="https://agentmods.dev/badge/skills/bop-clocktower/canary/canary-setup-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,261 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.00133 $0.02261
Opus 5 $0.00067 $0.01130
Sonnet 5 $0.00027 $0.00452
Haiku 4.5 $0.00013 $0.00226

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

Security

Grade A, and why

canary-setup-harness 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 9d 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-setup-harness/SKILL.md · 264 lines

How it starts

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

Canary: Setup Harness

Configure the Harness Engineering guardrails in a new Canary project (or a fork). Installs the harness CLI, initialises the config, wires up CI workflows, and verifies all gates pass on a clean repository.

When to Use

  • When setting up Canary (or a fork) in a new repository for the first time
  • When onboarding a new project that wants Canary's CI gate structure
  • When a fork has drifted from the harness config and needs to be re-aligned
  • NOT for day-to-day harness updates — use the harness CLI's own update flow for that
  • NOT for adding a single new gate to an existing config — edit harness.config.json directly
  • NOT for troubleshooting a failing CI check — see the Understanding the Harness wiki page

Process

Phase 1: PREREQUISITES — Confirm the Environment

  1. Verify Node.js is available (harness CLI requires it):

    node --version

    Version 18 or later is required.

  2. Verify Python is available (security ledger script):

    python3 --version

    Version 3.11 or later is required.

  3. Confirm the repo has a harness.config.json at the root. If it doesn't, the harness is not yet configured — continue to Phase 2. If it does, validate it first:

    npx --yes -p @harness-engineering/cli harness validate

    If validation passes, the harness is already set up. Stop here unless re-alignment is the goal.

Phase 2: INSTALL — Run the Harness Init

  1. Initialise the harness from the repo root:

    npx --yes -p @harness-engineering/cli harness init

    This creates harness.config.json with default gates and generates the .harness/ hooks directory.

  2. Review the generated harness.config.json. The defaults are sensible, but confirm:

    • layers matches the project's actual package structure (for Canary: llm, core, cli)
    • entrypoints lists the correct top-level packages
    • telemetry and adoption settings match team policy

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

  1. 9d ago First seen · 264 lines · 133 tokens per session scan A dfd90ecf776a

Subscribe to this mod's changes

canary-setup-harness is a skill published in the GitHub repository bop-clocktower/canary (4 stars, last pushed today), licensed MIT. It adds 133 tokens to every session and 2,261 once invoked, about $0.0007 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.

CI and CDDevOps and cloudTesting
Related

Other skills, from other repositories

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…

dotnet/skills · 191 tokens

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…

onsi/ginkgo · 132 tokens

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.

zebbern/claude-code-guide · 48 tokens

playwright-testing

E2E testing with Playwright - Page Objects, cross-browser, CI/CD.

alinaqi/maggy · 20 tokens

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…

UKGovernmentBEIS/inspect_evals · 120 tokens

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.

Donchitos/Claude-Code-Game-Studios · 49 tokens