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 vasilyu1983/AI-Agents-public --skill qa-api-testing-contractsgit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/qa-api-testing-contracts)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/qa-api-testing-contracts"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/qa-api-testing-contracts/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/qa-api-testing-contracts"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/qa-api-testing-contracts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.02865 |
| Opus 5 | $0.00022 | $0.01432 |
| Sonnet 5 | $0.00009 | $0.00573 |
| Haiku 4.5 | $0.00004 | $0.00286 |
Grade A, and why
qa-api-testing-contracts 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 5d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA API Testing and Contracts
Use this skill to turn API artifacts into enforceable checks: linting, breaking-change detection, executable contracts, negative/security coverage, and release gates that stop unsafe changes from shipping.
Quick Reference
| Need | Go to |
|---|---|
| Run the contract-testing workflow | ## Workflow |
| Gather the right API inputs first | ## Inputs to Gather |
| Check release-gate quality | ## Quality Checks |
| Load templates and references | ## Navigation |
Inputs to Gather
- Contract surface and canonical artifact for each surface:
- REST: OpenAPI 3.1 or 3.2
- GraphQL: SDL plus schema registry if used
- gRPC:
.protoplusbuf.yaml - Async/event flows: AsyncAPI
- Multi-step workflows: Arazzo
- Webhooks/callbacks: OpenAPI webhooks or AsyncAPI channels
- Where each artifact lives in-repo and whether generated artifacts exist in CI.
- Environments, auth methods, webhook signing model, and stable test identities/keys.
- Critical operations, messages, and workflows ranked by business risk.
- Data constraints: idempotency, ordering, pagination/cursors, retries, eventual consistency, rate limits, state convergence after backend changes, and DLQ/replay behavior.
- Versioning/deprecation policy, consumer inventory, and any operation registry or broker/registry already in use.
- Current tooling and CI policy: what blocks PR merge, release promotion, and production deploy.
Outputs (What to Produce)
- A minimal gate set for PR and release: lint + breaking diff + contract checks + promotion gate.
- A coverage map derived from the canonical artifacts, with critical operations and workflows first.
- A negative/security baseline aligned to OWASP API risks plus webhook/event-specific failure modes.
- An explicit quota and degraded-mode matrix for critical endpoints (for example
429/Retry-After, fallback body shape, and state-transition convergence checks).
Quick Start
- Identify the source-of-truth artifacts and remove drift between fragments, generated files, and runtime behavior.
- Lint every artifact before writing tests.
- Add breaking-change checks against the base branch on every PR.
- Choose an enforcement mix:
- CDC: Pact / PactFlow
- Schema-driven: Specmatic / Microcks
- Property-based hardening for HTTP APIs: Schemathesis
- Add minimum negative/security cases for auth, validation, error contracts, rate limits, webhooks, and async replay behavior.
- Make release gates explicit:
- Pact
can-i-deploy - GraphQL schema plus operations checks
buf breaking- Executable async/workflow contract checks
- Pact
What ships with it
18 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.
- agents/openai.yaml 374 B
- assets/api-test-plan.md 2.5 KB
- assets/contract-change-checklist.md 1.8 KB
- assets/schema-validation-matrix.md 3.7 KB
- data/sources.json 14 KB
- learnings.consolidated.md 600 B
- learnings.md 361 B
- references/advanced-contract-patterns.md 12 KB
- references/ai-contract-testing.md 5.9 KB
- references/api-security-testing.md 2.5 KB
- references/api-versioning-strategies.md 5.8 KB
- references/contract-testing-patterns.md 9.1 KB
- references/schema-driven-testing.md 5.4 KB
- scripts/buf_breaking_check.sh 1.1 KB runs code
- scripts/pact_can_i_deploy.sh 1.3 KB runs code
- scripts/README.md 5.1 KB
- scripts/schemathesis_baseline.sh 1.6 KB runs code
- scripts/spectral_lint.sh 1.1 KB runs code
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.
- 5d ago First seen · 209 lines · 44 tokens per session scan A 936ba47e3f97
qa-api-testing-contracts is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 6d ago), licensed MIT. It adds 44 tokens to every session and 2,865 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-03.
Other skills, from other repositories
add-handler
Scaffold a new HTTP handler with service function, store method (if needed), and table-driven test, following the project's internal/{api,service,store} layout. Invoke when the user asks to add an endpoint, handler, or route.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or…
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.