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/johnqtcg/awesome-skillsnpx agentmods add skills/johnqtcg/awesome-skills/api-integration-testWrote 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/johnqtcg/awesome-skills/api-integration-test)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/api-integration-test"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/api-integration-test/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/johnqtcg/awesome-skills/api-integration-test"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/api-integration-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 256 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00058 | $0.05694 |
| Opus 5 | $0.00029 | $0.02847 |
| Sonnet 5 | $0.00012 | $0.01139 |
| Haiku 4.5 | $0.00006 | $0.00569 |
Grade A, and why
api-integration-test 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 9d 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 — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integration Test
Goal
Build production-representative, opt-in integration tests for internal APIs with strict safety controls, reproducible execution, and clear failure diagnosis.
When To Use
Trigger this skill when the user asks for:
- Internal API integration tests (HTTP or gRPC)
- Service-to-service adapter tests requiring real runtime config
- Internal endpoint contract verification against real responses
- Integration test failure triage or debugging
Scope
Use this skill for:
- Internal HTTP API integration tests.
- Internal gRPC client/server integration tests.
- Service-to-service adapter tests requiring real runtime config.
- Internal endpoint contract verification against real responses.
Do not use this skill for:
- Pure unit tests with heavy mocks — use
$unit-test. - Full end-to-end browser journeys.
- Third-party vendor API tests — use
$thirdparty-api-integration-test.
Mandatory Gates
Gates execute in strict serial order. Any gate failure blocks all subsequent steps.
1) Scope 2) Go Version 3) Config 4) Mode
Validation ──→ Gate ──→ Completeness ──→ Selection
│ │ │ │
out of scope? read go.mod Full/Scaffold/ auto-select
→ stop+redirect → adapt Blocked? Smoke/Std/Comp
Blocked → STOP
│ │ │ │
5) Production 6) Execution 7) Reference
Safety ──→ Integrity ──→ Loading
│ │ │
prod? env+host actually ran? load by trigger
→ t.Fatalf → report pattern
1) Scope Validation Gate
Confirm the task falls within this skill's scope:
- Internal HTTP or gRPC API → proceed
- Pure unit test → redirect to
$unit-test, STOP - Third-party vendor API → redirect to
$thirdparty-api-integration-test, STOP - Full end-to-end browser journey → out of scope, inform user, STOP
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.
- references/advanced-patterns.md 5.8 KB
- references/checklists.md 4.5 KB
- references/common-integration-gate.md 6.1 KB
- references/common-output-contract.md 1.4 KB
- references/internal-api-patterns.md 6.3 KB
- scripts/run_regression.sh 644 B runs code
- scripts/tests/COVERAGE.md 6.3 KB
- scripts/tests/golden/001_simple_http_get.json 349 B
- scripts/tests/golden/002_grpc_service.json 324 B
- scripts/tests/golden/003_retryable_endpoint.json 298 B
- scripts/tests/golden/004_production_safety.json 260 B
- scripts/tests/golden/005_missing_config_degradation.json 275 B
- scripts/tests/golden/006_ci_github_actions.json 308 B
- scripts/tests/golden/007_expected_failure_paths.json 296 B
- scripts/tests/golden/008_data_lifecycle.json 221 B
- scripts/tests/test_behavioral_integration.py 20 KB runs code
- scripts/tests/test_golden_scenarios.py 7.5 KB runs code
- scripts/tests/test_skill_contract.py 21 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.
- 9d ago First seen · 453 lines · 58 tokens per session scan A 34d5afbbf00f
api-integration-test is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 5,694 once invoked, about $0.0003 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-30.
Other skills, from other repositories
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
verification-engine
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
eval-harness
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles.
dependency-upgrade
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
webapp-testing
Write and run comprehensive web app tests — unit, integration, E2E with Playwright/Cypress, and visual regression.
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.