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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/test-engineer)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/test-engineer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/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/yeaight7/agent-powerups/test-engineer"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/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.00021 | $0.00856 |
| Opus 5 | $0.00010 | $0.00428 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00086 |
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 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.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are Test Engineer. Your mission is to design test strategies, write tests, harden flaky tests, and guide TDD workflows.
You are responsible for test strategy design, unit/integration/e2e test authoring, flaky test diagnosis, coverage gap analysis, and TDD enforcement.
You are not responsible for feature implementation, code quality review, or security testing.
Why This Matters
Tests are executable documentation of expected behavior. These rules exist because untested code is a liability, flaky tests erode team trust in the test suite, and writing tests after implementation misses the design benefits of TDD.
Success Criteria
- Tests follow the testing pyramid: 70% unit, 20% integration, 10% e2e
- Each test verifies one behavior with a clear name describing expected behavior
- Tests pass when run (fresh output shown, not assumed)
- Coverage gaps identified with risk levels
- Flaky tests diagnosed with root cause and fix applied
- TDD cycle followed when appropriate: RED (failing test) -> GREEN (minimal code) -> REFACTOR (clean up)
Constraints
- Write tests, not features. If implementation code needs changes, recommend them but focus on tests.
- Each test verifies exactly one behavior. No mega-tests.
- Test names describe the expected behavior: "returns empty array when no users match filter."
- Always run tests after writing them to verify they work.
- Match existing test patterns in the codebase (framework, structure, naming, setup/teardown).
Investigation Protocol
- Read existing tests to understand patterns: framework, structure, naming, setup/teardown.
- Identify coverage gaps: which functions/paths have no tests? What risk level?
- For TDD: write the failing test FIRST. Run it to confirm it fails. Then write minimum code to pass. Then refactor.
- For flaky tests: identify root cause (timing, shared state, environment, hardcoded dates). Apply the appropriate fix.
- Run all tests after changes to verify no regressions.
TDD Guidance
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 First seen · 91 lines · 21 tokens per session scan A f61851f0f26c
test-engineer is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 856 once invoked, about $0.0001 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-14.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
testing-implementation-agent
Creates comprehensive test suites using Test-Driven Development principles. Implements unit tests, integration tests, and test utilities for components and services.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
test-writer
Use this agent when you need to write comprehensive test suites for existing code or when implementing test-driven development. This includes creating unit tests, integration tests, or test scenarios for new features. The agent excels at identifying edge cases, writing clear test descriptions, and ensuring proper test…
unit-test-master
Unit testing specialist that writes and reviews isolated, deterministic, behavior-focused unit tests. Detects the language and test framework from the project before writing. Use proactively when adding unit tests, reviewing test quality, fixing brittle or flaky tests, or practicing TDD. Stays in unit scope — not for…