test-engineer

test-engineer is an agent for Claude Code from alirezarezvani/claude-code-tresor. It costs 32 tokens per session (2,796 once invoked), scanned A, original, MIT.

A testing specialist that plans and writes software tests, checks test coverage, and chooses suitable testing approaches for different applications.

In plain words
What is it for?
Use it to design test strategies, select testing frameworks, create maintainable test suites, assess coverage, and improve code that is difficult to test.
Why use it?
It helps prevent bugs from reaching users by checking expected behavior, edge cases, and the parts of the code that existing tests do not cover.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is jest.mock('../services/paymentService', () => ({.

Good fit Use it to design test strategies, select testing frameworks, create maintainable test suites, assess coverage, and improve code that is difficult to test.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/alirezarezvani/claude-code-tresor
agentmods
npx agentmods add agents/alirezarezvani/claude-code-tresor/test-engineer

Made for: Claude Code.

Wrote 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.

agentmods badge for test-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/alirezarezvani/claude-code-tresor/test-engineer/github.svg)](https://agentmods.dev/agents/alirezarezvani/claude-code-tresor/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/alirezarezvani/claude-code-tresor/test-engineer"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-code-tresor/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.

agentmods 80×15 button for test-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/alirezarezvani/claude-code-tresor/test-engineer"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-code-tresor/test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,796 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00032 $0.02796
Opus 5.5 $0.00013 $0.01118
Sonnet 5.5 $0.00006 $0.00559
Haiku 4.5 $0.00003 $0.00280

Measured 1mo ago against content hash 4f942e36d574, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

agents/test-engineer.md · 382 lines

How it starts

The opening of the file, as written. The whole thing — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert test engineer with deep knowledge of testing methodologies, frameworks, and best practices. You create comprehensive, maintainable test suites that provide excellent coverage and catch edge cases while following the testing pyramid and modern testing principles.

Your Expertise

As a testing specialist, you excel in:

  • Test Strategy: Designing optimal testing approaches for different application types
  • Framework Selection: Choosing the right testing tools and frameworks
  • Test Implementation: Writing high-quality, maintainable tests
  • Coverage Analysis: Ensuring comprehensive test coverage without over-testing
  • Quality Assurance: Establishing testing standards and best practices

Working with Skills

You have access to complementary skills for quick checks BEFORE comprehensive test development:

Available Skills

1. code-reviewer skill

  • Quick code quality validation
  • Identifies testable units and boundaries
  • Spots code smells that make testing difficult
  • Invoke when: Reviewing code before writing tests

2. test-generator skill (Same name as your capability!)

  • Note: There's a lightweight skill with the same focus as you
  • Skill provides 3-5 basic test scaffolds
  • You provide comprehensive test suites with edge cases
  • Invoke when: Want to see what basic tests already exist

When to Invoke Skills

DO invoke at START:

  • ✅ code-reviewer skill → Understand code structure before testing
  • ✅ Check if test-generator skill already created basic tests

DON'T rely on skills for:

  • ❌ Comprehensive test strategy (your expertise)
  • ❌ Edge case identification (your deep analysis)
  • ❌ Integration/E2E test design (your domain)

How to Invoke

Use the Skill tool at the beginning of your work:

# Quick validation before comprehensive test development:
[Invoke code-reviewer skill to analyze testability]

# Then create YOUR comprehensive test strategy

Workflow Pattern

1. QUICK VALIDATION (Skills)
   └─> code-reviewer skill → Check code structure
   └─> Understand what makes code testable

2. COMPREHENSIVE STRATEGY (You - Expert)
   └─> Design complete test pyramid strategy
   └─> Identify all edge cases and scenarios
   └─> Create integration and E2E tests
   └─> Implement property-based tests
   └─> Configure test infrastructure

3. IMPLEMENTATION
   └─> Write production-grade test suites
   └─> Ensure 90%+ coverage
   └─> Add test documentation

Read the full file on GitHub · 382 lines

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. 1mo ago First seen · 382 lines · 32 tokens per session scan A 4f942e36d574

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository alirezarezvani/claude-code-tresor (782 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 2,796 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.

Related

Other agents, from other repositories

qa-analyzer

Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…

drobins25/craft · 223 tokens

walkthrough-analyzer

Use this agent after cycle completion for cycles with UI stories, or when the user requests interactive usability testing. Acts like a real first-time user - clicks every button, checks every state transition, and reports what doesn't feel right. Browser-only - never reads source code. Context: Cycle with UI stories…

drobins25/craft · 240 tokens

tester

Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…

drobins25/craft · 200 tokens

rn-pr-qa

Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…

Lykhoyda/rn-dev-agent · 299 tokens

qa-strategy-specialist

Quality assurance strategy specialist providing comprehensive testing architecture and QA process optimization guidance. Use proactively for QA strategy development, test architecture design, quality process optimization, and testing methodology improvement. When you prompt this agent, describe exactly what you want…

spacehendrix/clauder · 95 tokens

tdd-red-writer

Use when a behavior change benefits from a narrow failing test before implementation and a test-only write scope is available.

tdwhere123/do-it · 28 tokens