Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yonatangross/orchestkitnpx agentmods add skills/yonatangross/orchestkit/testing-integrationWrote 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/yonatangross/orchestkit/testing-integration)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/testing-integration"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/testing-integration.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.00049 | $0.02550 |
| Opus 5 | $0.00024 | $0.01275 |
| Sonnet 5 | $0.00010 | $0.00510 |
| Haiku 4.5 | $0.00005 | $0.00255 |
Grade A, and why
testing-integration 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 yesterday.
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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration & Contract Testing
Focused patterns for testing API boundaries, cross-service contracts, component integration, database layers, property-based verification, and schema validation.
Quick Reference
For complex emulate setups (full config generation, webhook HMAC, CI per-worker port isolation), delegate to the
emulate-engineersubagent. Pairs with theemulate-seedskill.
| Area | Rule / Reference | Impact |
|---|---|---|
| Stateful API testing (emulate) | rules/emulate-stateful-testing.md |
HIGH |
| API endpoint tests | rules/integration-api.md |
HIGH |
| React component integration | rules/integration-component.md |
HIGH |
| Database layer testing | rules/integration-database.md |
HIGH |
| Zod schema validation | rules/validation-zod-schema.md |
HIGH |
| Pact contract testing | rules/verification-contract.md |
MEDIUM |
| Stateful testing (Hypothesis) | rules/verification-stateful.md |
MEDIUM |
| Evidence & property-based | rules/verification-techniques.md |
MEDIUM |
References
| Topic | File |
|---|---|
| House rules not documented upstream | references/ork-delta.md |
| Consumer-side Pact tests | references/consumer-tests.md |
| Hypothesis strategies guide | references/strategies-guide.md |
Checklists
| Checklist | File |
|---|---|
| Contract testing readiness | checklists/contract-testing-checklist.md |
| Property-based testing | checklists/property-testing-checklist.md |
Scripts & Templates
| Script | File |
|---|---|
| Create integration test | scripts/create-integration-test.md |
Examples
| Example | File |
|---|---|
| Full testing strategy | examples/orchestkit-test-strategy.md |
Upstream coverage (do not restate)
This skill wraps Pact, the Pact Broker, and FastAPI testing. It carries only the OrchestKit delta. Fetch the vendor docs for the topics below instead of restating them here.
What ships with it
17 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.
- checklists/contract-testing-checklist.md 2.4 KB
- checklists/property-testing-checklist.md 1.7 KB
- examples/orchestkit-test-strategy.md 18 KB
- references/consumer-tests.md 3.8 KB
- references/ork-delta.md 5.6 KB
- references/strategies-guide.md 3.4 KB
- rules/_sections.md 1.5 KB
- rules/emulate-stateful-testing.md 3.3 KB
- rules/integration-api.md 4.1 KB
- rules/integration-component.md 1.9 KB
- rules/integration-database.md 1.7 KB
- rules/validation-zod-schema.md 2.4 KB
- rules/verification-contract.md 2.2 KB
- rules/verification-stateful.md 2.3 KB
- rules/verification-techniques.md 4.1 KB
- scripts/create-integration-test.md 1.7 KB
- test-cases.json 2.7 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.
- yesterday First seen · 284 lines · 49 tokens per session scan A 77ff4fabf51a
testing-integration is a skill published in the GitHub repository yonatangross/orchestkit (229 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 2,550 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-09-05.
Other skills, from other repositories
api-contract-tester
Implement consumer-driven contract testing with Pact to ensure API compatibility.
Contract-First Testing
Contract-first testing approach using Pact, Spring Cloud Contract, or Dredd for ensuring API consumer-provider compatibility.
api-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
contract-testing
Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing. Use when testing API contracts or coordinating distributed teams.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.
API Versioning Testing
Testing API versioning strategies including URL path, header, and query parameter versioning with backward compatibility validation.