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/saitarrun/devforge-ai/contract-testingnpx skills add saitarrun/Devforge-ai --skill contract-testinggit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00023 | $0.00351 |
| Opus 5 | $0.00012 | $0.00176 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
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 2d 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
Contract Testing & OpenAPI Validation Skill
This skill ensures microservices communicate reliably via explicit, version-controlled contracts without breaking downstream consumers.
Core Architectural Pillars
1. OpenAPI & Schema Drift Validation
- Spec-First & Code-First Sync: Enforce strict TypeScript/Zod/JSON Schema generation from OpenAPI 3.1 definitions.
- Breaking Change Detection: Run
oasdifforopenapi-diffin CI/CD to block backward-incompatible changes (e.g. removed fields, altered types, tightened validation).
2. Consumer-Driven Contract Testing (Pact)
- Consumer Contracts: Downstream microservices define expected API requests and responses.
- Provider Verification: Upstream microservice verifies actual endpoint execution against consumer expectations before deployment.
- Pact Broker Matrix: Track deployment status across environments to prevent deploying incompatible service versions.
3. Mock Service Worker (MSW) & Integration Mocks
- Deterministic API Fixtures: Shared MSW handlers across unit, component, and E2E tests.
- Network Level Interception: Mock API traffic at network level to avoid fragile global fetch overrides.
Checklist for Slices with needs_contract_testing: true
- OpenAPI 3.1 schema defined or updated
- Breaking change check passes against
mainbranch schema - Consumer Pact tests generated or MSW handlers synchronized
- Provider endpoint verification passes end-to-end
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.
- 2d ago First seen · 31 lines · 23 tokens per session scan A 9fb33b9acdbd
contract-testing is a skill published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 23 tokens to every session and 351 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
skill-code-quality
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
skill-developer-relations
SDK development, external developer communication, code samples, API client libraries, community engagement, and developer experience. Use when creating SDKs, writing external guides, creating code samples, or improving developer experience.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
skill-architecture
This skill should be used when the user asks to "design a system", "architecture", "ADR", "system design", "tech stack", "choose between approaches", "coupling", "service granularity", "blueprint", "component design", "API contract", "schema design", "trade-offs", or discusses "monolith", "microservices", "fitness…
skill-accessibility
WCAG 2.1 AA compliance, keyboard navigation, screen reader testing, semantic HTML, ARIA labels, color contrast, assistive technology validation. Use when ensuring accessibility, conducting a11y audits, testing with screen readers, or designing inclusive interfaces.