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 agentmods add skills/developersglobal/ai-agent-skills/integration-testingnpx skills add DevelopersGlobal/ai-agent-skills --skill integration-testinggit clone --depth 1 https://github.com/DevelopersGlobal/ai-agent-skillsWrote 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/developersglobal/ai-agent-skills/integration-testing)<a href="https://agentmods.dev/skills/developersglobal/ai-agent-skills/integration-testing"><img src="https://agentmods.dev/badge/skills/developersglobal/ai-agent-skills/integration-testing.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 | $0.00028 | $0.00640 |
| Opus 5 | $0.00014 | $0.00320 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
integration-testing 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Unit tests verify components work in isolation. Integration tests verify they work together. The gap between these two is where most production bugs hide. This skill ensures integration tests cover the real system boundaries.
When to Use
- After unit tests are passing
- Before any feature ships to production
- When testing database, API, or third-party service interactions
Process
Step 1: Identify Real Boundaries
- Map every boundary in the system: code ↔ database, code ↔ external API, service ↔ service, frontend ↔ backend.
- Rank boundaries by failure impact.
- Integration tests should cover the top 5 highest-impact boundaries.
Verify: Boundary map created. Top 5 prioritized.
Step 2: Test Real, Not Mocked
- Use a real test database (not SQLite in-memory if prod uses PostgreSQL).
- Use contract tests for external APIs — test against a recorded real response.
- Use test containers for services that would otherwise require mocking.
- Mock only: third-party services you can't control, slow services with contract tests already in place.
Verify: No internal boundaries are mocked in integration tests.
Step 3: Test the Happy Path AND Failure Cases
- Happy path: the system works end-to-end for the primary use case.
- Failure cases: database down, API returns 500, timeout, malformed response.
- State verification: after each action, verify the state in the real database.
Verify: At least 1 failure case per boundary is tested.
Step 4: Keep Tests Independent
- Each test cleans up its own state (transactions rolled back, test data deleted).
- Tests don't share state with each other.
- Tests can run in any order.
Verify: Test suite passes when run in random order.
Common Rationalizations (and Rebuttals)
| Excuse | Rebuttal |
|---|---|
| "Unit tests are enough" | Unit tests with mocks test that your mocks work, not your system. |
| "Integration tests are slow" | Slow tests are better than discovering bugs in production. Optimize the setup, not the coverage. |
| "We test in staging" | Staging is not a substitute for automated tests. It's too slow and too manual. |
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.
- 4d ago First seen · 74 lines · 28 tokens per session scan A 0f68a8902ef9
integration-testing is a skill published in the GitHub repository DevelopersGlobal/ai-agent-skills (65 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 640 once invoked, about $0.0001 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
code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
constraint-driven-development
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or…
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
code-simplification
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now…