Borrowing it
Nothing to install: this file belongs to waalwalker1/regulated-mcp-insurance-deployment. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/waalwalker1/regulated-mcp-insurance-deployment/main/.agents/skills/test-first-contract/SKILL.mdgit clone --depth 1 https://github.com/waalwalker1/regulated-mcp-insurance-deploymentWrote 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/waalwalker1/regulated-mcp-insurance-deployment/test-first-contract)<a href="https://agentmods.dev/skills/waalwalker1/regulated-mcp-insurance-deployment/test-first-contract"><img src="https://agentmods.dev/badge/skills/waalwalker1/regulated-mcp-insurance-deployment/test-first-contract/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/waalwalker1/regulated-mcp-insurance-deployment/test-first-contract"><img src="https://agentmods.dev/badge/skills/waalwalker1/regulated-mcp-insurance-deployment/test-first-contract.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.00017 | $0.00114 |
| Opus 5 | $0.00009 | $0.00057 |
| Sonnet 5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
test-first-contract 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 11d 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
Test First Contract
For every P0 capability:
- state the invariant in plain English;
- write a failing test or acceptance check;
- implement the minimal real behavior;
- make the test pass;
- add a negative/edge case;
- map the test to the evidence ledger.
Do not chase global coverage percentages. Prioritize business invariants, security boundaries, data provenance, error handling, and public demo flows.
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.
- 11d ago First seen · 18 lines · 17 tokens per session scan A a21f3ec65562
test-first-contract is a skill published in the GitHub repository waalwalker1/regulated-mcp-insurance-deployment (0 stars, last pushed 20d ago), licensed MIT. It adds 17 tokens to every session and 114 once invoked, about $0.0001 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.
Other skills, from other repositories
implement
Implement a specification using a TDD-oriented workflow. Extracts requirements, generates tests first, then implements to pass the tests. Includes spiral detection and acceptance gates.
dev-pipeline
Issue → Explore → Plan → TDD (Red→Green→Refactor) → Benchmark → PR → Review.
prespec
Write the behaviour specification for a feature BEFORE implementing it, as test cases. Use whenever you are about to build a new endpoint, screen, flow, or behaviour — especially anything touching auth, sessions, tokens, lists, or pagination. Also use when asked "how should I test this", "what should this actually…
Test Driven Development
Strict Red-Green-Refactor implementation methodology for high quality, regression-free software.
testing
Comprehensive software testing skill covering unit tests, integration tests, TDD/BDD, mocking strategies, and test automation across multiple languages. Use this skill when writing test cases, designing test strategies, implementing test automation, or need guidance on testing frameworks and best practices. Ideal for…
tdd
Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly…