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 pnakhat/qa-ai-repo --skill api-contract-testinggit clone --depth 1 https://github.com/pnakhat/qa-ai-repoWrote 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/pnakhat/qa-ai-repo/api-contract-testing)<a href="https://agentmods.dev/skills/pnakhat/qa-ai-repo/api-contract-testing"><img src="https://agentmods.dev/badge/skills/pnakhat/qa-ai-repo/api-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.00115 | $0.01942 |
| Opus 5 | $0.00057 | $0.00971 |
| Sonnet 5 | $0.00023 | $0.00388 |
| Haiku 4.5 | $0.00012 | $0.00194 |
Grade A, and why
api-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 8d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Contract Testing
Contract testing verifies that two services agree on the interface without standing up both in a slow, flaky end-to-end environment. It catches breaking changes at the boundary — the highest-value, lowest-cost API tests.
Pick the approach
| Situation | ✅ Approach |
|---|---|
| You own the consumers; internal microservices | Consumer-driven (Pact) — each consumer declares exactly what it needs; provider verifies against all of them |
| Public API, many/unknown consumers, a spec is the source of truth | Spec-first (OpenAPI/AsyncAPI) — validate real traffic conforms to the spec in both directions |
| You publish a spec and have known internal consumers | Both — spec-first for the public surface, Pact for the internal consumers |
| Event/message boundary (Kafka, AMQP, WebSocket) | Message pacts (consumer-driven) or AsyncAPI (spec-first) |
| GraphQL | Schema-diff breaking-change detection (GraphQL Inspector / Rover checks) |
Consumer-driven asks "what does each consumer actually use?" and only verifies
that. Spec-first asks "does traffic match the published contract?" — necessary
when you can't enumerate consumers. See tooling.md for the tool matrix.
Consumer-driven (Pact) workflow
- Consumer test: write an interaction (request → expected response) against a Pact mock; run the consumer's real client code against it. This generates a pact file — assert on shape/types, not exact values (use matchers).
- Publish the pact (with consumer version + git sha + branch/tag) to a Pact Broker / PactFlow.
- Provider verification: the provider replays every consumer interaction against its real implementation, using provider states to set up data.
can-i-deploy: before releasing either side, query the broker to confirm the version is compatible with everything it will meet in the target env. Block the deploy if not.
Spec-first workflow
- Treat the OpenAPI/AsyncAPI spec as the contract; lint it (Spectral) in CI.
- Provider side: assert responses conform to the spec — property-based fuzzing (Schemathesis) or replaying the spec's examples (Dredd).
- Consumer side: run against a spec-driven mock (Prism) so consumers develop against the contract, not a live service.
- Detect breaking changes: diff the spec against the last released version
(e.g.
oasdiff) and fail CI on backward-incompatible changes.
What ships with it
2 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.
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.
- 8d ago First seen · 139 lines · 115 tokens per session scan A e5f3ab475e1e
api-contract-testing is a skill published in the GitHub repository pnakhat/qa-ai-repo (2 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 1,942 once invoked, about $0.0006 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
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
convex-test
Generate convex-test tests for the app's Convex functions.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.