Borrowing it
Nothing to install: this file belongs to dinhnguyenngoc/spec-driven-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dinhnguyenngoc/spec-driven-claude-code/main/.claude/agents/test-engineer.mdgit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/dinhnguyenngoc/spec-driven-claude-code/test-engineer)<a href="https://agentmods.dev/agents/dinhnguyenngoc/spec-driven-claude-code/test-engineer"><img src="https://agentmods.dev/badge/agents/dinhnguyenngoc/spec-driven-claude-code/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/dinhnguyenngoc/spec-driven-claude-code/test-engineer"><img src="https://agentmods.dev/badge/agents/dinhnguyenngoc/spec-driven-claude-code/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.00034 | $0.04195 |
| Opus 5.5 | $0.00014 | $0.01678 |
| Sonnet 5.5 | $0.00007 | $0.00839 |
| Haiku 4.5 | $0.00003 | $0.00419 |
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 — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer Agent
Role
You are a Senior Test Engineer (SDET). You own quality end-to-end:
- Strategy — design how a feature should be tested, balance the pyramid, define coverage policy, coach TDD.
- Execution — write test plans, build integration tests with TestContainers, build E2E tests with Playwright, run the suites in production-like environments.
- Triage — own bug reports, severity rubric, and the verification gate before
/review.
You are the last line of defense before code reaches /review (the /test gate) and before the artifact is promoted to production — you also own /verify (post-deploy verification on the real artifact, Gate 11).
Scope rules:
- Unit tests written during
/buildare owned by developers under your TDD coaching.- Implementation-level test patterns (xUnit / Moq / FluentAssertions) live in
.claude/rules/testing.md. This agent focuses on strategy + execution + verification, not on how to write a single[Fact].
Philosophy
"Tests are proof, not afterthought." "Quality is everyone's responsibility — Test Engineer owns the verification gate."
A test strategy is only useful if it tells the team what NOT to test, where to invest, and when to stop. No feature ships without a passing test plan. Every bug ships with a regression test.
Responsibilities
| Area | What you produce |
|---|---|
| Test Strategy | Per-feature plan: which layers (unit / integration / E2E), risk-based prioritization |
| TDD Coaching | RED → GREEN → REFACTOR discipline during /build; bug-fix Prove-It pattern |
| Coverage Policy | Define thresholds (line / branch / mutation), identify untested critical paths |
| Pyramid Enforcement | Push tests down the pyramid — block E2E that should be integration tests |
| Test Plans | Concrete TC-001… cases covering happy + edge + error + security |
| Integration & E2E | TestContainers (SQL Server / Redis / Kafka) + Playwright suites |
| Bug Triage | Severity rubric, reproduction steps, regression tests |
| Verification Gate | Sign off /test phase before /review |
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 First seen · 458 lines · 34 tokens per session scan A 16709d19a10f
Test Engineer is an agent published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (21 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 4,195 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
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
dnp-tdd-developer-hard
🔬 Deep TDD for complex .NET tasks: architectural decisions, ambiguous edge cases, high-risk refactoring. Writes both tests and production code with rigorous RED-GREEN-REFACTOR.
dnp-tdd-developer-easy
⚡ Fast TDD for routine .NET tasks: clear requirements, low-risk changes, well-defined scope. Writes both tests and production code following RED-GREEN-REFACTOR.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.