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-rulesgit 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-rules)<a href="https://agentmods.dev/skills/chohra-med/expo_boilerplate/spec-harness-rules"><img src="https://agentmods.dev/badge/skills/chohra-med/expo_boilerplate/spec-harness-rules/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-rules"><img src="https://agentmods.dev/badge/skills/chohra-med/expo_boilerplate/spec-harness-rules.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.00099 | $0.00404 |
| Opus 5 | $0.00049 | $0.00202 |
| Sonnet 5 | $0.00020 | $0.00081 |
| Haiku 4.5 | $0.00010 | $0.00040 |
Grade A, and why
spec-harness-rules 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 12d 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-rules
Make per-directory rules exist and resolve them. --scan: at each rules-boundary dir (own manifest/stack) generate a RULES.md with the 5 concern sections from that dir's real code, never copied across stacks. --check <path>: print the merged rules an agent would see (root→…→dir, deepest wins). The build flow scans first so subagents resolve, not invent.
Run it
- Load the full procedure — read the command doc and follow it exactly:
.claude/commands/spec-harness/rules.md(this repo) or the spec-harness sourcecommands/rules.md. - Agents — spawn from
.claude/agents/: researcher, implementer. - 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.
- 12d ago First seen · 21 lines · 99 tokens per session scan A 39d1d356f0d2
spec-harness-rules is a skill published in the GitHub repository chohra-med/expo_boilerplate (34 stars, last pushed 10d ago), licensed MIT. It adds 99 tokens to every session and 404 once invoked, about $0.0005 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-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.
monorepo-dev-workflow
Use when building, testing, linting, formatting, typechecking, or running any app or package in the ffmpeg-video-composer monorepo, or when looking for the right pnpm/vp command.
Detox React Native Testing
End-to-end testing for React Native apps using Detox with gray-box testing, synchronization, device simulation, and CI integration.
react-native-brownfield-migration
Provides an incremental adoption strategy to migrate native iOS or Android apps to React Native or Expo using @callstack/react-native-brownfield for initial setup. Use when planning migration steps, packaging XCFramework/AAR artifacts, and integrating them into host apps.
react-native-core
React Native core components, layout, styling, animations, lists, platform APIs, and best practices. Use when building iOS/Android UIs with native components.
upgrading-react-native
Upgrades React Native apps to newer versions by applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. Use when upgrading React Native, bumping RN version, updating from RN 0.x…