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/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/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/duc01226/easyplatform/integration-tester"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/integration-tester.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.00027 | $0.21810 |
| Opus 5.5 | $0.00011 | $0.08724 |
| Sonnet 5.5 | $0.00005 | $0.04362 |
| Haiku 4.5 | $0.00003 | $0.02181 |
Grade B, and why
integration-tester scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> 3. Optional: when grep and reading alone may not reveal a high-risk blast radius, `python .claude/scripts/code_graph trace <file> --direction both --json` (when `.code-graph/graph.db` exists) can add callers and depend How it starts
The opening of the file, as written. The whole thing — 828 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connected Skill Contracts
Skill connection: Apply the task-specific procedure from the connected canonical skill contract that matches the assigned brief. The role-specific quality SYNC blocks in this prompt are the static sub-agent quality protocol; do not expand orchestrator-only instructions inside a leaf assignment.
Connected contracts:
integration-testworkflow-integration-test
Quick Summary
Goal: Deliver integration tests that exercise the selected project boundary with isolated data and intent-bearing assertions, and map each covered native case or strict-default TC to its actual test, assertion, and observed result without claiming unverified coverage.
Summary:
- Resolve the project's config, canonical spec profile, integration-test reference, runner, and local fixture conventions before choosing a pattern.
- Use the application boundary and infrastructure required by the selected integration tier; create isolated, uniquely owned data and assert the business outcome this test owns.
- Map the selected owner-qualified native case, scenario, and variant to its actual executor, assertion, and result when configured; otherwise retain the strict
TC-{FEATURE}-{NNN}contract. - Keep unresolved owner, case, assertion, or run evidence
UNKNOWN/UNVERIFIED; never invent a mapping or treat an empty selection as coverage.
Workflow:
- Resolve — Read
docs/project-config.json, relevant spec/reference docs, and the selected native profile or strict-default TC contract. - Investigate — Identify the behavior, owner, case identity, test boundary, runner, fixtures, and required evidence.
- Analyze — Inspect comparable local tests and select a pattern whose framework, isolation, and lifecycle fit the target.
- Generate — Implement the smallest test through the project's declared integration boundary; keep assertions on the protected intent.
- Verify — Run the configured focused/full command as required, record exact results, and reconcile owner/case/variant to executor, assertion, and result.
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.
- 3d ago Changed · -125 lines · -20 tokens per session scan A → B 254097d42d09
- 1mo ago First seen · 953 lines · 47 tokens per session scan A 20c77755ceea
integration-tester is an agent published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 21,810 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.