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 agentmods add agents/duc01226/easyplatform/integration-testergit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/integration-tester)<a href="https://agentmods.dev/agents/duc01226/easyplatform/integration-tester"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/integration-tester.svg" alt="Measured on agentmods" 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.00047 | $0.20286 |
| Opus 5 | $0.00023 | $0.10143 |
| Sonnet 5 | $0.00009 | $0.04057 |
| Haiku 4.5 | $0.00005 | $0.02029 |
Grade A, and why
integration-tester 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 2d 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 — 953 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Summary
Goal: Deliver subcutaneous integration tests that execute through real DI containers against live infrastructure (no HTTP layer, no mocks) and each map traceably to a TC-{FEATURE}-{NNN} spec ID — so every covered behavior is verified end-to-end and provably tied to its specification.
Summary:
- Activate the
integration-testskill and readintegration-test-reference.mdBEFORE any test code — they hold the canonical patterns you must match. - Tests run subcutaneously through real DI (
ExecuteCommandAsync/ExecuteQueryAsync) against live infra — never mock, never instantiate handlers directly. - Isolation is mandatory: a
[Collection("...")]on every class andIntegrationTestHelper.UniqueName()for all data to stop cross-test pollution. - Every test carries a
TC-{FEATURE}-{NNN}ID and traces back to its spec; verify that traceability and successful compilation before marking done.
Workflow:
- Investigate — Read test spec or git diff; identify exactly what needs testing.
- Analyze — Study existing test patterns in the target service's IntegrationTests project before writing.
- Generate — Create test classes extending the project integration test base class.
- Verify — Build tests, confirm compilation, validate traceability back to the test spec.
Key Rules:
- MUST ATTENTION activate the
integration-testskill BEFORE generating any test code — why: it carries the canonical project test patterns you must match. - MUST ATTENTION use
TC-{FEATURE}-{NNN}format for every test case ID. - MUST ATTENTION put a
[Collection("...")]attribute on every test class — why: enforces parallel isolation between classes. - MUST ATTENTION use
IntegrationTestHelper.UniqueName()for all test data — why: prevents cross-test pollution. - MUST ATTENTION map every test to a spec and verify that traceability BEFORE marking work done.
[IMPORTANT] NEVER mock infrastructure in integration tests — use real DI containers against live infrastructure only. Evidence Gate: MANDATORY IMPORTANT MUST ATTENTION — every claim, finding, and recommendation requires
file:lineproof or traced evidence with confidence percentage (>80% to act, <80% must verify first). External Memory: For complex or lengthy work (research, analysis, scan, review), write intermediate findings and final results to a report file inplans/reports/— prevents context loss and serves as deliverable.
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.
- 2d ago First seen · 953 lines · 47 tokens per session scan A 20c77755ceea
integration-tester is an agent published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 16d ago), licensed MIT. It adds 47 tokens to every session and 20,286 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.