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 45ck/skill-harness --skill verify-interpretergit clone --depth 1 https://github.com/45ck/skill-harnessWrote 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/45ck/skill-harness/verify-interpreter)<a href="https://agentmods.dev/skills/45ck/skill-harness/verify-interpreter"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/verify-interpreter/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/45ck/skill-harness/verify-interpreter"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/verify-interpreter.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.00025 | $0.00941 |
| Opus 5.5 | $0.00010 | $0.00376 |
| Sonnet 5.5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
verify-interpreter 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read and explain the output of specgraph verify in plain language, then recommend next steps.
Status meanings
| Status | Meaning | Action |
|---|---|---|
PASS |
All required evidence thresholds met | Nothing required |
WARN |
Evidence exists but below required strength for this state | Strengthen evidence or lower requirement |
FAIL |
No evidence found for a required dimension | Add evidence or add waiver |
INSUFFICIENT |
Evidence found but strength is below required level | Raise evidence strength (e.g. E0 → E2) |
SKIP |
Spec has no evidence requirements (draft/deprecated) | Review if state is correct |
WAIVED |
Requirement waived — check expiry | Verify waiver is still valid |
Example output
PASS FEAT-001 [accepted]
WARN FEAT-002 [in_progress]
warn: No verification claims found (advisory)
FAIL FEAT-003 [accepted]
fail: No implementation claims found. Required: E2 (indexed)
INSUFFICIENT FEAT-004 [accepted]
insufficient-evidence: implementation: found E0 but required E2
Verify commands reference
specgraph verify # summary table for all specs
specgraph verify --spec FEAT-001 # single spec only
specgraph verify --json # machine-readable output
specgraph verify --changed src/foo.ts # incremental scan (changed files only)
specgraph verify --no-db # dry run — skip writing to DB
specgraph explain <SPEC-ID> # full claim breakdown for one spec
specgraph explain # all specs
specgraph find --spec FEAT-001 # locate files that reference a spec
specgraph find --relation IMPLEMENTS # all IMPLEMENTS claims
specgraph find --provider annotation # claims from a specific provider
specgraph find --strength 1 # E1 and above
specgraph waivers # list active waivers
specgraph waivers FEAT-001 # waivers for one spec
specgraph subject issue:beads:bd-a1b2 # show a specific Beads issue's claims
specgraph subject symbol:annotation:MyClass # show a symbol's claims
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.
- 1mo ago First seen · 79 lines · 25 tokens per session scan A fe07c46488fa
verify-interpreter is a skill published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 941 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
do-it-verify
Use when selecting evidence for a delivery claim, regression fix, installation, or branch closeout.
vibe
Use when working in a vibe-coded repository, where the user never reads the code and only runs the product and gives feedback, or when the user wants to start building a project that way.
testing-bun
Use when writing or modifying tests in a Bun project.
testing-ink
Use when writing or modifying tests for Ink (terminal UI) components.
testing-react
Use when writing or modifying tests for React hooks.
instructions
Use at the start of any task, before taking action, to load the always-on workflow rules covering skill invocation, communication, skill scripts, and the conventions of the environment the session is running in.