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 chohra-med/expo_boilerplate --skill spec-harness-verifygit clone --depth 1 https://github.com/chohra-med/expo_boilerplateWrote 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/chohra-med/expo_boilerplate/spec-harness-verify)<a href="https://agentmods.dev/skills/chohra-med/expo_boilerplate/spec-harness-verify"><img src="https://agentmods.dev/badge/skills/chohra-med/expo_boilerplate/spec-harness-verify/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/chohra-med/expo_boilerplate/spec-harness-verify"><img src="https://agentmods.dev/badge/skills/chohra-med/expo_boilerplate/spec-harness-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.00327 |
| Opus 5.5 | $0.00026 | $0.00131 |
| Sonnet 5.5 | $0.00013 | $0.00065 |
| Haiku 4.5 | $0.00007 | $0.00033 |
Grade A, and why
spec-harness-verify 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.
What it actually says
spec-harness-verify
Spawn the sdd-verifier with a clean context. It runs each goal.md end-state check literally (no inference) and emits RESULT: PASS|FAIL + evidence. It must not be the agent that wrote the code.
Run it
- Load the full procedure — read the command doc and follow it exactly:
.claude/commands/spec-harness/verify.md(this repo) or the spec-harness sourcecommands/verify.md. - Agents — spawn from
.claude/agents/: verifier. - Stay inside the 3 pillars — memory bank (
.memory/) · Spec-Driven Development · Harness (ratchetAGENTS.md+ verifier + learning loop). ReadSPEC-HARNESS.mdfor how this repo is wired.
Non-negotiables
- The ratchet only tightens (rules are append/sharpen, never drop).
- Nothing is "done" until the separate verifier returns PASS against
goal.md. - Every correction or FAIL cause goes through
spec-harness-learn→ a dated rule. - Never scaffold the second-brain vault. Never commit a client repo unless asked.
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 · 21 lines · 66 tokens per session scan A e77a78b225b8
spec-harness-verify is a skill published in the GitHub repository chohra-med/expo_boilerplate (36 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 327 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
react-native-testing
Deep React Native Testing Library (RNTL) reference — v13 (React 18 sync) and v14 (React 19 async), queries, userEvent, matchers, anti-patterns.
react-native-e2e-testing
End-to-end testing for React Native and Expo with Maestro — YAML flows, testID selectors, subflows and scripting, permissions and deep links, E2E builds, CI on EAS Workflows and GitHub Actions, and flakiness control. Detox notes for gray-box needs.
jest-unit
Unit testing skill using Jest for TypeScript and JavaScript, covering mocking, spies, snapshots, coverage, async testing, and custom matchers.
integration-e2e-testing
Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary. Use when writing or reviewing E2E or integration tests.
typescript-testing
Applies repository-aware TypeScript test design, behavior evidence, isolation, and mock-boundary criteria. Use when writing or reviewing unit tests.
frontend-typescript-testing
Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest, and Playwright when present. Use when adding or reviewing component, loading/error-state, integration, or frontend E2E tests.