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 SebastienDegodez/skraft-plugin --skill contract-testinggit clone --depth 1 https://github.com/SebastienDegodez/skraft-pluginWrote 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/sebastiendegodez/skraft-plugin/contract-testing)<a href="https://agentmods.dev/skills/sebastiendegodez/skraft-plugin/contract-testing"><img src="https://agentmods.dev/badge/skills/sebastiendegodez/skraft-plugin/contract-testing.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.1 | $0.00043 | $0.03694 |
| Opus 5 | $0.00022 | $0.01847 |
| Sonnet 5 | $0.00009 | $0.00739 |
| Haiku 4.5 | $0.00004 | $0.00369 |
Grade A, and why
contract-testing 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 6d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/01-openapi-json-body.md 5.9 KB
- examples/02-openapi-js-dispatcher.md 8.5 KB
- examples/03-testcontainers-dotnet.md 9.9 KB
- examples/04-asyncapi-kafka.md 12 KB
- references/artifact-bridging.md 6.6 KB
- references/asyncapi-contract-workflow.md 7.8 KB
- references/contract-verification.md 7.2 KB
- references/dispatchers-reference.md 6.1 KB
- references/microcks-testcontainers-setup.md 7.5 KB
- references/openapi-samples-authoring.md 6.6 KB
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.
- 6d ago First seen · 434 lines · 43 tokens per session scan A 1ebe9af4a7db
contract-testing is a skill published in the GitHub repository SebastienDegodez/skraft-plugin (8 stars, last pushed yesterday), licensed GPL-3.0. It adds 43 tokens to every session and 3,694 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
generate-microcks-openapi-samples
Use when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses.
api-tester
Test and document API endpoints - validate responses, check status, generate examples.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
Contract Test Generator
Generate consumer-driven contract tests using Pact framework to verify API provider-consumer compatibility and prevent integration breaking changes.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.
api-testing-rest
Comprehensive RESTful API testing patterns covering HTTP methods, status codes, request/response validation, authentication, error handling, and contract testing.