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 agentmods add skills/flurdy/agent-skills/contract-testnpx skills add flurdy/agent-skills --skill contract-testgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/contract-test)<a href="https://agentmods.dev/skills/flurdy/agent-skills/contract-test"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/contract-test.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.03116 |
| Opus 5 | $0.00019 | $0.01558 |
| Sonnet 5 | $0.00008 | $0.00623 |
| Haiku 4.5 | $0.00004 | $0.00312 |
Grade A, and why
contract-test 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 4d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Test (Pact-Lite)
Consumer-driven contract testing without a broker. Contracts are JSON files exchanged directly between consumer and provider services via the filesystem.
When to Use
- After modifying a connector, API client, or endpoint interface (request/response models, URLs, headers)
- When adding a new REST endpoint that other services will consume
- To verify contracts haven't broken after upstream/downstream changes
- When a consumer or provider test is failing and you need to re-sync contracts
- After bulk changes that touch multiple services — run project-wide to verify all contracts
Usage
/contract-test # Auto-detect: run contract tests for current service
/contract-test consumer # Run consumer tests to generate contract files
/contract-test sync # Copy generated contracts to provider services
/contract-test provider # Run provider verification against current contracts
/contract-test full # Single-service: consumer + sync + provider for current service
/contract-test full all # Multi-service: ALL consumers → sync → normalize → ALL providers
/contract-test full <svc> <svc> # Multi-service: named consumers → sync → normalize → affected providers
/contract-test status # Show contract test coverage and staleness
Concepts
Consumer-Driven Contracts (Pact-Lite)
This is a lightweight version of the Pact workflow that works without a broker:
- Consumer services define expected interactions with providers in test code
- Consumer tests generate contract files (JSON) describing those expectations
- Contract files are copied from consumer to provider (no broker — just filesystem)
- Provider services verify they satisfy all consumer contracts
Roles
- Consumer: A service that calls another service's API. Generates
.jsoncontract files. - Provider: A service that exposes an API. Verifies contracts from its consumers.
- A service can be both consumer and provider for different dependencies.
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.
- 4d ago First seen · 342 lines · 39 tokens per session scan A bb8e02bdba46
contract-test is a skill published in the GitHub repository flurdy/agent-skills (7 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 3,116 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…