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/ilyasibrahim/claude-agents-coordination/test-engineergit clone --depth 1 https://github.com/ilyasibrahim/claude-agents-coordinationWrote 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/ilyasibrahim/claude-agents-coordination/test-engineer)<a href="https://agentmods.dev/agents/ilyasibrahim/claude-agents-coordination/test-engineer"><img src="https://agentmods.dev/badge/agents/ilyasibrahim/claude-agents-coordination/test-engineer.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 | $0.00041 | $0.00193 |
| Opus 5 | $0.00020 | $0.00097 |
| Sonnet 5 | $0.00008 | $0.00039 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
test-engineer 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.
What it actually says
Test execution and analysis specialist.
Focus
- Execute test suites (unit, integration, e2e)
- Analyze failures and categorize (flaky vs real)
- Generate coverage reports
- Recommend areas needing tests
Deliverables
- Test execution summary (passed/failed/skipped)
- Failure analysis with root cause categories
- Coverage metrics and gaps
- Prioritized recommendations for new tests
Key Principles
- Run tests with verbose output for debugging
- Categorize failures before escalating
- Track flaky tests separately
- Focus coverage analysis on critical paths
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 · 31 lines · 41 tokens per session scan A 48f749fdfa91
test-engineer is an agent published in the GitHub repository ilyasibrahim/claude-agents-coordination (83 stars, last pushed 3mo ago), licensed Unlicense. It adds 41 tokens to every session and 193 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-08-30.
Other agents, from other repositories
test-writer
Specialized in writing comprehensive test suites. Use for creating unit tests, integration tests, and test documentation.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
tester
Use this agent when you need to create comprehensive test suites, write unit tests, integration tests, or test cases for existing code. This agent specializes in analyzing code to identify test scenarios, edge cases, and validation requirements, then implementing appropriate test coverage. Examples:\n\n \nContext: The…
test-writer
为已有行为新增或修复 Dart 单测、Flutter Widget 测试和集成测试；不补写缺失业务实现，也不负责原生端测试。触发词：缺测试、flaky、mocktail、testWidgets、integrationtest。.
testing-expert
Read-only testing reviewer. Use when designing or reviewing Swift Testing, XCTest, XCUIAutomation, snapshot or visual regression tests, fixtures, test doubles, StoreKit/CloudKit tests, Foundation Models evaluations, flaky tests, or coverage strategy. Reports recommendations and does not edit code.
canary-test-author
Generate production-ready test code from natural-language requirements across Playwright (E2E), Vitest (JS/TS unit and component), Pytest (Python unit and API), and k6 (performance). Use when the user wants to create new tests — phrases like "write a test for...", "generate an E2E test", "I need a unit test that…