integration-test-plan

integration-test-plan is a skill for Codex from jeremylongworth-source/AgentSkills. It costs 45 tokens per session (286 once invoked), scanned A, original, MIT.

A planning guide for testing how multiple parts of a system work together, such as APIs, databases, queues, services, and external connections. These are integration tests, which check boundaries between components rather than one small function alone.

In plain words
What is it for?
Use it to design test environments, fixtures, dependency fakes, seeded data, cleanup, CI coverage, and success and failure cases.
Why use it?
It helps catch failures in data storage, permissions, retries, contracts, and dependencies that isolated unit tests may miss.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to design test environments, fixtures, dependency fakes, seeded data, cleanup, CI coverage, and success and failure cases.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeremylongworth-source/agentskills/integration-test-plan
Install

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.

Any agent
npx skills add jeremylongworth-source/AgentSkills --skill integration-test-plan
Clone the repo
git clone --depth 1 https://github.com/jeremylongworth-source/AgentSkills

Made for: Codex.

Wrote 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.

agentmods badge for integration-test-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/integration-test-plan/github.svg)](https://agentmods.dev/skills/jeremylongworth-source/agentskills/integration-test-plan)
Your own site
<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.

agentmods 80×15 button for integration-test-plan

Your own site · 80×15
<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>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 286 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00286
Opus 5 $0.00023 $0.00143
Sonnet 5 $0.00009 $0.00057
Haiku 4.5 $0.00005 $0.00029

Measured 7d ago against content hash 229e9013db65, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 7d 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.

skills/integration-test-plan/SKILL.md · 43 lines

What it actually says

Integration Test Plan

Core Workflow

  1. Identify interacting components, data stores, external services, queues, auth, and contracts under test.
  2. Define test environment, fixtures, dependency fakes, seeded data, and cleanup strategy.
  3. Cover success, failure, retry, permission, persistence, and contract-change cases.
  4. Decide which dependencies should be real, fake, mocked, or containerized.
  5. Include test commands, CI fit, and data isolation needs.
  6. 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.md when designing integration test coverage.
Files

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.

Changes

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.

  1. 7d ago First seen · 43 lines · 45 tokens per session scan A 229e9013db65

Subscribe to this mod's changes

integration-test-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 286 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.

Related

Other skills, from other repositories

firebase-development-add-feature

This skill should be used when adding features to existing Firebase projects. Triggers on "add function", "create endpoint", "new tool", "add api", "new collection", "implement", "build feature". Guides TDD workflow with test-first development, security rules, and emulator verification.

aiskillstore/marketplace · 64 tokens

firebase-development-add-feature

This skill should be used when adding features to existing Firebase projects. Triggers on "add function", "create endpoint", "new tool", "add api", "new collection", "implement", "build feature". Guides TDD workflow with test-first development, security rules, and emulator verification.

aiskillstore/marketplace · 64 tokens

dependency-injection

Use when writing or reviewing code with object graphs, service dependencies, or testability concerns. Covers constructor injection, DI containers, lifetimes, and anti-patterns (service locator, ambient context, over-injection).

andr-ca/agentharness · 47 tokens

api-contract-checker

Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.

proflead/codex-skills-library · 25 tokens

authos-backend-integration

Secure backend APIs with AuthOS-issued JWTs and the AuthOS Node server adapter. Use when building an API that must verify AuthOS bearer tokens, enforce JWT claims, add Express middleware, validate JWKS keys, or create a backend-owned session after a browser OAuth callback.

drmhse/authos_skill · 62 tokens

authos-device-flow

Implement AuthOS device authorization for CLIs, TVs, and headless apps. Use when requesting device codes, building activation pages, polling /auth/token, handling MFA during device auth, or adding platform admin CLI login through AuthOS.

drmhse/authos_skill · 52 tokens