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 squall-chua/skills --skill integration-testgit clone --depth 1 https://github.com/squall-chua/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/squall-chua/skills/integration-test)<a href="https://agentmods.dev/skills/squall-chua/skills/integration-test"><img src="https://agentmods.dev/badge/skills/squall-chua/skills/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/squall-chua/skills/integration-test"><img src="https://agentmods.dev/badge/skills/squall-chua/skills/integration-test.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.00044 | $0.03730 |
| Opus 5.5 | $0.00018 | $0.01492 |
| Sonnet 5.5 | $0.00009 | $0.00746 |
| Haiku 4.5 | $0.00004 | $0.00373 |
Grade A, and why
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 2mo 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A seam is where your code hands work to something it does not own — a database, a broker, a cache, another team's API. Unit tests stop at the seam and mock what is on the far side, so everything they prove is a statement about your own mock. This skill writes the tests that cross it and run against the real thing.
Real infrastructure makes tests slow and flaky unless they are hermetic: each test brings
its own data, leaves nothing behind, and passes alone, shuffled, and twice in a row. A suite
without that property gets marked skip within a month. Both halves are the job — cross the
seam, and stay hermetic while doing it.
What this skill writes
New test files, the harness that starts the real dependencies, and one report. The production code stays as it is: a test that can only pass after the source changes has found a bug, and that goes in the report as a finding for its owner.
1. Inventory the seams
Read the wiring, not the whole codebase: where clients are constructed, what the config and environment variables name, what the container or compose files declare, what the manifest lists as a driver or SDK.
| Seam | Looks like |
|---|---|
| Database | a connection string, an ORM, a migration folder, raw SQL |
| Cache | Redis, Memcached, a client with a TTL |
| Broker or stream | Kafka, RabbitMQ, SQS, NATS, an outbox table |
| Object store | S3, GCS, Azure Blob, a signed-URL helper |
| Third-party API | an SDK, a base URL in config, a webhook receiver |
| Another service you own | an internal base URL, a generated client |
| Filesystem | a path from config, a temp directory, an upload folder |
Rank them the same way risk is ranked anywhere: what the seam decides — money, permissions, data writes — and how often the code around it changes:
git log --since='6 months ago' --name-only --format= -- <path> | grep . | sort | uniq -c | sort -rn
The grep . matters: --name-only prints a blank line between commits, and without it the
blank sorts to the top as your busiest file.
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.
- 2mo ago First seen · 324 lines · 44 tokens per session scan A 893bdb1a0fb4
integration-test is a skill published in the GitHub repository squall-chua/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 3,730 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-08-31.
integration-test compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| integration-testsquall-chua/skills | Skill | 2 | 1mo ago | MIT | A | 44 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |