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 jeremylongworth-source/AgentSkills --skill integration-test-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/integration-test-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/integration-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/integration-test-plan/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/jeremylongworth-source/agentskills/integration-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/integration-test-plan.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00286 |
| Opus 5.5 | $0.00018 | $0.00114 |
| Sonnet 5.5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
integration-test-plan 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 1mo 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
Integration Test Plan
Core Workflow
- Identify interacting components, data stores, external services, queues, auth, and contracts under test.
- Define test environment, fixtures, dependency fakes, seeded data, and cleanup strategy.
- Cover success, failure, retry, permission, persistence, and contract-change cases.
- Decide which dependencies should be real, fake, mocked, or containerized.
- Include test commands, CI fit, and data isolation needs.
- Record gaps that need E2E, load, or manual verification.
Safety Rules
- Do not use production systems, production data, or real customer credentials.
- Do not run destructive integration tests without isolated test resources.
- Do not hide flaky dependency risks.
Deliverable Shape
For integration test plans, provide:
- Components and boundaries
- Environment and fixtures
- Dependency strategy
- Test matrix
- Data setup and cleanup
- CI and command notes
- Gaps and follow-up tests
References
- Read
references/integration-test-plan-checklist.mdwhen designing integration test coverage.
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.
- 1mo ago First seen · 43 lines · 45 tokens per session scan A 229e9013db65
integration-test-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 45 tokens to every session and 286 once invoked, about $0.0002 per session on Opus 5.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
writing-springboot-tests
Use when writing or adding tests for Spring Boot code at a service's edges: HTTP clients that call other services (WireMock: 4xx and 5xx responses, timeouts, retries), Kafka or RabbitMQ listeners (redelivery, poison messages, dead-letter topics), events published to other services, or full-API tests against real…
add-module
Adds a new application module to this Spring Modulith project with the package layout the ModuleBoundariesTests gate expects, and a module-scoped integration test. Use when the user asks for a new module, bounded context, or feature area that doesn't belong in an existing module.
backend-manual-testing
Use when the task touches a backend API, database or worker - booting it from the task branch, driving real requests and verifying side effects (DB rows, outbound calls, logs) as evidence.
worker-job-testing
Use when the task has a background job, queue consumer, scheduler or webhook - firing the real trigger, polling for the side effect, and the retry, idempotency and poison-message cases.
backend-runtime-check
Use before handing off any change to an endpoint, job or migration — start the service from the task branch and exercise the change with real requests, real logs and real DB side effects.
api-contract-testing
Use when a task adds or changes an HTTP endpoint, its request/response shape, status codes, auth or error format - the request matrix, curl templates and what counts as a contract break.