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 DauQuangThanh/hanoi-rainbow --skill integration-testinggit clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/integration-testing)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/integration-testing"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/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/dauquangthanh/hanoi-rainbow/integration-testing"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/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.00091 | $0.00626 |
| Opus 5 | $0.00046 | $0.00313 |
| Sonnet 5 | $0.00018 | $0.00125 |
| Haiku 4.5 | $0.00009 | $0.00063 |
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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Testing
Overview
Designs comprehensive integration testing strategies including API testing, database testing, microservices testing, end-to-end testing, and test automation frameworks
Core Capabilities
- Core Capability 1 - Description
- Core Capability 2 - Description
- Core Capability 3 - Description
Quick Start
Basic Workflow:
- Analyze requirements and context
- Apply appropriate patterns
- Validate and test results
- Document findings and recommendations
Detailed Topics
Load reference files based on specific needs:
-
Activation Guidelines: See activation-guidelines.md when:
- Working with related functionality
- Need specific patterns or examples
- Require detailed guidance
-
Cicd Integration: See cicd-integration.md when:
- Working with related functionality
- Need specific patterns or examples
- Require detailed guidance
-
Core Capabilities: See core-capabilities.md when:
- Working with related functionality
- Need specific patterns or examples
- Require detailed guidance
-
Integration Testing Process: See integration-testing-process.md when:
- Working with related functionality
- Need specific patterns or examples
- Require detailed guidance
-
Test Coverage And Reporting: See test-coverage-and-reporting.md when:
- Working with related functionality
- Need specific patterns or examples
- Require detailed guidance
-
Test Patterns: See test-patterns.md when:
- Working with related functionality
- Need specific patterns or examples
- Require detailed guidance
-
Testing Best Practices: See testing-best-practices.md when:
- Working with related functionality
- Need specific patterns or examples
- Require detailed guidance
What ships with it
9 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.
- references/activation-guidelines.md 579 B
- references/cicd-integration.md 23 KB
- references/core-capabilities.md 1.4 KB
- references/integration-testing-process.md 25 KB
- references/test-coverage-and-reporting.md 782 B
- references/test-patterns.md 19 KB
- references/testing-best-practices.md 1.3 KB
- references/testing-frameworks-and-tools.md 614 B
- references/testing-frameworks.md 23 KB
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.
- 9d ago First seen · 76 lines · 91 tokens per session scan A 186edb9d81b6
integration-testing is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 91 tokens to every session and 626 once invoked, about $0.0005 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-31.
Other skills, from other repositories
spec-driven-development
Spec-first workflow where an executable, testable specification is written before code and becomes the single source of truth that tests verify against, flowing spec → acceptance criteria → tasks → implementation.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
gsd-verify-work
Validate built features through conversational UAT.