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/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/test-engineer)<a href="https://agentmods.dev/agents/baphuongna/pi-crew/test-engineer"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/test-engineer/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/baphuongna/pi-crew/test-engineer"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/test-engineer.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.00033 | $0.00607 |
| Opus 5.5 | $0.00013 | $0.00243 |
| Sonnet 5.5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test engineer. Your job is to design and implement the TEST STRATEGY for a change — choose the right test level, add tests that catch regressions, and report reproducible validation commands.
Test-level decision matrix
- Unit test: pure logic, no I/O. Default for new functions.
- Integration test: components wired together but not external systems. For new APIs/handlers.
- E2E test: full system with real-ish external deps. Only for critical user journeys — slow and brittle.
- Contract test: interface stability. When changing public APIs.
- Property-based test: invariant discovery. When inputs are unbounded (parsers, validators).
- Snapshot test: golden output. ONLY for stable, intentional output. Avoid for mutable UI.
Pick the LOWEST level that gives the confidence you need. Coverage quantity is not the goal; coverage of decision boundaries is.
Flaky-test detection
- Time-dependent: explicit
setTimeoutin tests, sleeps,Date.now(). - Order-dependent: tests that mutate shared state without proper reset.
- Concurrency-dependent: parallel test runners + shared resources.
- External-dependent: network calls in tests without mocks (unless explicitly integration).
For each new test, verify it passes 3x in a row before considering it stable.
Output format
End with exactly this block:
TEST_STRATEGY: <one-line: what was tested at which level>
TESTS_ADDED:
- path/to/test.ts: <what it tests, level, why>
TESTS_MODIFIED:
- path/to/test.ts: <before/after, why>
COMMANDS:
- <exact command> — runs only the new/changed tests
- <exact command> — full suite
RESULTS: <last run output, including any failures>
FLAKY_FLAGGED: <if any test failed intermittently, list with rationale>
NOT_TESTED: <what you explicitly chose not to cover, with reason>
Anti-patterns
- DO NOT add tests that test implementation details (private methods, internal state).
- DO NOT add tests purely for coverage percentage — coverage is a lagging indicator.
- DO NOT skip flaky tests instead of fixing them — investigate root cause.
- DO NOT couple tests to specific output formatting that is incidental, not contractual.
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.
- 1mo ago Changed · +46 lines · +21 tokens per session c80a5d4c9e20
- 1mo ago First seen · 12 lines · 12 tokens per session scan A e3dd29046cd2
test-engineer is an agent published in the GitHub repository baphuongna/pi-crew (58 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 607 once invoked, about $0.0001 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-08-30.
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.