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 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/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/developersglobal/ai-agent-skills/integration-testing"><img src="https://agentmods.dev/badge/skills/developersglobal/ai-agent-skills/integration-testing.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.00028 | $0.00640 |
| Opus 5.5 | $0.00011 | $0.00256 |
| Sonnet 5.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 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.
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.
- 1mo 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 (177 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 640 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
constraint-driven-development
A development method for writing a project's quality standards as a lasting, checkable contract. It can cover areas such as test coverage, security, performance, accessibility, and architecture.
test-driven-development
Instructions for test-driven development, or TDD: writing a failing test first, then the smallest code that makes it pass, followed by cleanup.
tdd
Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).
browser-testing-with-devtools
A guide for testing web pages and browser-based applications in a real Chrome browser through Chrome DevTools. It checks what is actually rendered and how the page behaves at runtime.