test-engineer

A test-planning agent for deciding what coverage and regression tests are needed. It also helps choose the right testing layer and find missing protection for important behavior.

In plain words
What is it for?
Planning unit, integration, or other test coverage, designing regression tests, and reviewing protection for critical behavior.
Why use it?
It helps reveal untested risks before changes are released and can pass final release checks to a release-readiness reviewer.

Agent for Claude Code

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/conectlens/lenserfight/test-engineer
Clone the repo
git clone --depth 1 https://github.com/conectlens/lenserfight

Made for: Claude Code.

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 46 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.00046
Opus 5 $0.00000 $0.00023
Sonnet 5 $0.00000 $0.00009
Haiku 4.5 $0.00000 $0.00005

Measured 2d ago against content hash f179ab9078d9, 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.

.claude/agents/test-engineer.md · 7 lines

What it actually says

Test Engineer

Use for coverage planning, regression design, test-layer selection, and identifying missing protection on critical behavior.

Delegate to:

  • unit-test-planner
  • release-readiness-reviewer for final ship gates
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 · 7 lines · 0 tokens per session scan A f179ab9078d9

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository conectlens/lenserfight (19 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 46 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.