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 irahardianto/awesome-agv --skill test-integrationgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/test-integration)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/test-integration"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/test-integration/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/irahardianto/awesome-agv/test-integration"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/test-integration.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.00042 | $0.00873 |
| Opus 5.5 | $0.00017 | $0.00349 |
| Sonnet 5.5 | $0.00008 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
test-integration 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve Integration Test Coverage
Entry-point guard: This is a user-invoked command skill (
/test-integration). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.
Purpose
Audit and improve integration test coverage for I/O adapters. For unit test gaps, use the /test-unit skill.
When to Use
- I/O adapters (database, HTTP clients, file system, message queues) lack integration tests
- New infrastructure components without integration tests
- Pre-release verification of adapter reliability
- After discovering adapter bugs in production
When NOT to Use
- Unit test gaps (use
/test-unitskill) - E2E test gaps (use
/test-e2eskill) - New feature development (use
/workflow-solo)
Phases
Phase 1: AUDIT
Objective: Map which adapters have integration tests and which don't.
- Scan codebase for I/O adapter patterns per @architectural-pattern.md: search for Repository, Store, Client, Adapter, Gateway, Provider in type/interface names. Also search for database drivers, HTTP clients, file system operations, message queue connections.
- For each discovered adapter, check for corresponding integration test file. Language-specific naming conventions come from the idiom skill (e.g., Go:
*_integration_test.go, TS:*.integration.spec.ts, Python:*_integration_test.py) - Produce Adapter Coverage Map artifact: adapter name, type (DB/HTTP/FS/Queue), has integration test (Y/N), test file path if exists
Gate: Adapter coverage map created. All I/O boundaries identified.
Phase 2: INFRASTRUCTURE
Objective: Set up test infrastructure for untested adapters.
- Load
testing-strategyskill for Testcontainers and infrastructure patterns - For each untested adapter, set up required infrastructure:
- Database adapters: Testcontainers with target database
- HTTP client adapters: Mock server or test endpoint
- File system adapters: Temp directory with cleanup
- Message queue adapters: Testcontainers with target broker
- Create shared test infrastructure setup (reusable across tests): container lifecycle, seed data scripts, connection factory for test environments
- If CI pipeline exists, verify integration tests can run in CI (reference
ci-cdskill)
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 · 85 lines · 42 tokens per session scan A 819ee430f66c
test-integration is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 873 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-10-15.
Other skills, from other repositories
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
uat-signoff
Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.
quality-engineering-appium-mcp
Drives iOS/Android mobile devices via Appium MCP. Runs a preflight, picks local emulator/simulator/USB or a device cloud, captures screenshots/page source into a named evidence dir. Use for verifying mobile bugs, E2E tests, and navigating real device clouds (LambdaTest/BrowserStack).
zephyr-coverage-analysis
Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.