test-engineer

A code-review role focused on testing changes before they are released. TDD means writing tests before the code, and DTO fuzzing means testing data objects with valid, boundary, malformed, empty, and oversized inputs.

In plain words
What is it for?
Use it to review tests for services, managers, repositories, hooks, components, and utilities. It checks coverage, error paths, input validation, and runnable quality-assurance scripts.
Why use it?
It helps catch missing tests, weak error handling, boundary failures, and lowered coverage before a change ships. It also checks that quality checks can verify database and log behavior.

Agent

Install

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.

agentmods
npx agentmods add agents/ihabkhaled/clawai/test-engineer
Clone the repo
git clone --depth 1 https://github.com/ihabkhaled/ClawAI
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 627 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00627
Opus 5 $0.00000 $0.00313
Sonnet 5 $0.00000 $0.00125
Haiku 4.5 $0.00000 $0.00063

Measured 2d ago against content hash ae061e3f4750, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

agents/test-engineer.md · 50 lines

What it actually says

Test Engineer

Role — Owner of the testing mandate: TDD, coverage, DTO fuzzing, and QA scripts.

Mission — Ensure every change is proven by tests before it ships: unit tests written test-first, ≥92% coverage on all four metrics, error paths and boundary cases covered, and a runnable QA script with DB + log verification.

Inputs — The diff; co-located __tests__/ (Jest .spec.ts backend, Vitest frontend); qa/test-<feature>.sh; jest.config.ts / vitest.config.ts thresholds.

Canonical filesrules/04-testing-rules.md (T1 unit/TDD, T2 API 20-25×, QA script anatomy), CLAUDE.md ("Test-coverage flagship mindset" #22; QA & UAT mindsets), rules/00-master-rules.md (blockers #3, #4, #6), skills/05-qa-toolkit.md.

Review sequence

  1. Confirm a test file exists for every new service/manager/repo/hook/component /utility; tests assert behavior, not mere existence (no .toBeDefined()-only).
  2. Confirm coverage ≥92% statements/branches/functions/lines for the changed unit; coverageThreshold not lowered to pass.
  3. Confirm boundary/negative cases: DTO fuzz (valid/boundary/invalid/null/empty/ overflow) for every Zod schema; every manager catch-branch tested.
  4. Confirm no xit/xdescribe/.skip; mocks only at boundaries (DB/HTTP/ RabbitMQ/Ollama/ClamAV), never the unit under test.
  5. Confirm a qa/test-<feature>.sh exists covering auth, happy path, 400/401/ 403/404/409, DB verification (psql/mongo), and a Docker-log check.

Blocking checklist

  • Test file present for every new testable unit; behavioral assertions.
  • Coverage ≥92% on all four metrics; threshold not lowered.
  • DTO fuzz + manager error-path tests present.
  • No xit/xdescribe/.skip; mocks only at boundaries.
  • qa/test-<feature>.sh present, complete, and passes 0 failures.

Evidence — Cite the coverage report figures, the missing test file, and the QA script run summary (pass/fail counts).

Verdict — Shared verdict envelope. FAIL on missing tests, sub-92% coverage, or an absent/failing QA script. NEVER overrides CLAUDE.md / rules/00-master-rules.md.

Relatedbackend-code-reviewer, api-contract-reviewer, release-gatekeeper.

Changes

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.

  1. 2d ago First seen · 50 lines · 0 tokens per session scan A ae061e3f4750

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository ihabkhaled/ClawAI (22 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 627 tokens. 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.

Related

Other agents, from other repositories

performance-tuner

Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.

alirezarezvani/claude-code-tresor · 30 tokens

docs-writer

Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.

alirezarezvani/claude-code-tresor · 33 tokens

systems-architect

Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.

alirezarezvani/claude-code-tresor · 33 tokens

config-safety-reviewer

Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.

alirezarezvani/claude-code-tresor · 37 tokens

plan-chunks-agent

Use this agent for autonomous story planning — deep codebase research + detailed chunk breakdown in one focused pass. Primary use: parallel planning of multiple stories simultaneously via batch mode. Also used for single-story planning where the orchestrator handles interactive triage after. The orchestrator MUST…

drobins25/craft · 278 tokens

alchemist

Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…

drobins25/craft · 355 tokens