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 gtapps/claude-code-hermit --skill claude-harness-canarygit clone --depth 1 https://github.com/gtapps/claude-code-hermitWrote 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/gtapps/claude-code-hermit/claude-harness-canary)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/claude-harness-canary"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/claude-harness-canary/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/gtapps/claude-code-hermit/claude-harness-canary"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/claude-harness-canary.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.00074 | $0.04418 |
| Opus 5 | $0.00037 | $0.02209 |
| Sonnet 5 | $0.00015 | $0.00884 |
| Haiku 4.5 | $0.00007 | $0.00442 |
Grade D, and why
claude-harness-canary scanned grade D with 2 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
"<project>/.claude/settings.local.json" permissions-sync Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Never use `rm -rf`. How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Harness Canary
Run all three groups serially against the currently installed Claude Code. Take no arguments and do not offer group selectors. Target 5–8 minutes, but preserve bounded waits and evidence over that estimate.
Keep this canary core-only, current-Claude-only, interactive-tmux-only, and loaded through --plugin-dir. Never add it to CI, release commands, or $pre-release-review.
Shared probe prerequisite
Reuse the installed $probe lifecycle. Before creating canary state, read its active SKILL.md and require all of these properties:
- real interactive Claude in tmux, never
claude -p, Codex, or another PTY; - no interactive
--no-session-persistence; tmux pipe-panestarts before any input;- one bounded readiness phase that detects the trust dialog, accepts it only when present, handles only explicitly recognized startup onboarding, and waits for the normal prompt;
- a unique output-only completion nonce whose complete value is never contiguous in the injected prompt;
- completion accepted only from assistant output after the requested evidence, never prompt echo;
- one bounded wait per canary action;
- teardown with
rm -ronly after validating the exact scratch path.
If any property is absent, stop before preflight and report:
PREREQUISITE BLOCKED — update the local $probe protocol
Do not recreate generic tmux lifecycle rules locally or hand-roll a fallback. Extend the probe lifecycle only for the multi-action assertions below.
Preflight
Run from the repository root.
-
Resolve the absolute core path at
plugins/claude-code-hermit. -
Record bounded output from:
claude --version claude --help tmux -V claude auth status --json -
Require current help to expose
--plugin-dir,--model,--permission-mode, and--session-id. -
Require authentication through the default profile. Do not set
CLAUDE_CONFIG_DIR. -
Require these core files:
.claude-plugin/plugin.jsonhooks/hooks.jsonscripts/lib/harness-command.tsscripts/stop-pipeline.tsscripts/hermit-watchdog.tsscripts/ask-gate.tsscripts/apply-settings.tsscripts/routines.tsscripts/routine-monitor.shskills/hermit-routines/SKILL.md
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.
- 5d ago Changed 89e46a83a64f
- 9d ago First seen · 386 lines · 74 tokens per session scan D 046520074ec0
claude-harness-canary is a skill published in the GitHub repository gtapps/claude-code-hermit (74 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 4,418 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
symfony:e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
symfony:functional-tests
Write functional tests for Symfony controllers and HTTP endpoints using WebTestCase, getContainer, loginUser, and DAMA rollback.
ccc-e2e
CC Commander · $ccc-e2e · Full-surface confidence before you ship.
ccc-qa
QA workflow. Runs unit + integration + E2E tests, coverage delta, edge case enumeration, flaky test quarantine. Delegates to qa-engineer agent.
playwright-expert
Use when writing or fixing E2E tests in a Playwright project - playwright.config.ts, .spec.ts files under tests/ or e2e/, @playwright/test imports - or right after implementing a frontend/backend change that needs an end-to-end proof. Writes and extends TypeScript E2E suites as the QA gate for feature and bug-fix…
journey-simulation
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…