test-engineer

A development agent that writes tests before implementation and adds tests where existing coverage is missing. Test-driven development, or TDD, is the practice of starting with a test that describes the desired behavior.

In plain words
What is it for?
Use it to create failing tests for new behavior, fill coverage gaps, and pass test artifacts to the next development step.
Why use it?
It catches incorrect behavior early and makes untested parts of the code visible.

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/foliveira/harmonia/test-engineer
Clone the repo
git clone --depth 1 https://github.com/foliveira/harmonia
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 180 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 84% copy Near-identical to another mod 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.00019 $0.00180
Opus 5 $0.00010 $0.00090
Sonnet 5 $0.00004 $0.00036
Haiku 4.5 $0.00002 $0.00018

Measured yesterday against content hash fde5d5900e3b, 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 yesterday.

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.

Origin

This is a copy

84% identical to committer — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/test-engineer.md · 23 lines

What it actually says

Read these two files before acting; together they are your working contract:

  1. ${CLAUDE_PLUGIN_ROOT}/core/RULES.md
  2. ${CLAUDE_PLUGIN_ROOT}/core/charters/test-engineer.md

If either file cannot be read, stop and report the failing path - do not proceed uncharted.

When prior experience could help, retrieve relevant learnings with:

bash ${CLAUDE_PLUGIN_ROOT}/bin/memory/recall.sh

Work only inside your charter's authority, read your inputs from the task workspace paths you are given, and write your outputs to the workspace paths your charter names - the next agent consumes files, not conversation.

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. yesterday First seen · 23 lines · 0 tokens per session scan A fde5d5900e3b

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository foliveira/harmonia (2 stars, last pushed 17d ago), licensed MIT. It adds 19 tokens to every session and 180 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to committer, differing in 8 lines, and is treated as a copy.

Related

Other agents, from other repositories

gsd-plan-checker

Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.

travisjneuman/.claude · 36 tokens

go-expert

Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.

travisjneuman/.claude · 69 tokens

cloud-architect

Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…

travisjneuman/.claude · 69 tokens

devsecops-engineer

CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…

travisjneuman/.claude · 83 tokens

devops-engineer

Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.

travisjneuman/.claude · 48 tokens

architecture-analyst

Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.

travisjneuman/.claude · 36 tokens