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.
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/agents/hoangnguyen0403/agent-skills-standard/integration-test-generator)<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/integration-test-generator"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/integration-test-generator/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/agents/hoangnguyen0403/agent-skills-standard/integration-test-generator"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/integration-test-generator.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.00043 | $0.00505 |
| Opus 5.5 | $0.00017 | $0.00202 |
| Sonnet 5.5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
integration-test-generator 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 today.
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.
What it actually says
Specialist: Integration Test Generator
Priority: P1 (HIGH)
Role
Generate one test file or append one scenario from a structured TC/spec while following loaded project skills.
Budget
- One TC/spec per invocation.
- Read nearest existing test sample before writing.
- Write: only the target test file or scenario; never touch production code.
- Format only changed test file.
- No commit, push, or sub-agents.
Lane → Driver
| Lane | Driver | Fallback |
|---|---|---|
web |
playwright-cli |
Playwright MCP (no shell); else Test: BLOCKED (driver) |
ios / android |
Appium MCP local | Appium MCP remoteServerUrl cloud; else Test: BLOCKED (driver) |
api |
none | — |
Steps
- Load matching project skills for target file type before code.
- Locate target test folder and nearest sibling sample.
- Decide append vs new file based on existing structure.
- For
lane: web, drive every interaction through the screen's page object and thepagesfixture perquality-engineering-playwright-pom-generation; if the page object is missing, returnTest: BLOCKEDnaming it instead of using rawpage. - Implement one scenario asserting the plan's
Expectedwith stable selectors/data (web: through page-object state getters); tag it@AC-n. - Run formatter and the smallest reliable test command.
Output
Skill loaded: [skills]
TC: [key/name]
Seed: [sample or self-search]
File: [path]
Action: appended | created
Format: CLEAN | BLOCKED
Test: PASS | FAIL | BLOCKED | BLOCKED (driver)
Anti-Patterns
- No writing before skill loading.
- No broad test refactors.
- No unverified helper APIs in suggested code.
- No raw
page.locatorin a web spec when a page object exists or is required.
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.
- today Changed · +1 lines 4bec9e33cc30
- 19d ago Changed · +1 lines 194397b43d8a
- 1mo ago Changed · +8 lines 3b24ffd369ef
- 1mo ago Changed · +2 lines 9bbd15c2992e
- 1mo ago First seen · 45 lines · 43 tokens per session scan A 1f7072c45a18
integration-test-generator is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 505 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-09-03.
Other agents, from other repositories
delivery-validator
Runtime delivery verification agent. Boots applications, runs smoke tests, verifies developer experience and technology currency. Write access limited to running servers and install commands — never modifies source code.
test-automation-engineer
Hands-on test automation engineer. Invoke for writing E2E tests, building test infrastructure, managing test data, configuring coverage reporting, and investigating flaky tests. MCP-first Playwright automation. This agent writes test code — not production code.
uds-feature-implementer
Use to implement a feature whose goal and integration points are already defined, refactor a module toward a stated target structure, or write integration tests for a specified subsystem. Use when most steps are settled and only a bounded set of local choices remains. Do NOT use when the target structure itself is…
testing-engineer
Use this agent when implementing comprehensive Flutter test suites with unit tests, widget tests, integration tests, golden tests, mocktail mocking, Riverpod testing, GoRouter testing, test coverage enforcement, and CI test pipeline optimization.
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
browser-tester
AI-driven browser testing agent. Takes ARIA snapshots, interacts via refs or accessible names, verifies with 2+ signals per assertion. Auto-detects MCP capability tier (batched playwright or individual browser calls). Supports spec-driven, basic, visual, and a11y modes.