test-engineer

A test-writing agent that creates maintainable tests for Python, JavaScript, TypeScript, and Go code, including tests with controlled outside services.

In plain words
What is it for?
Use it to create unit or integration tests, mock APIs and databases, test asynchronous code, or generate parameterized and property-based tests.
Why use it?
It helps developers test behavior, edge cases, errors, and side effects while avoiding unreliable tests that fail unpredictably.

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/dachivadachkoria/claude-code-starter-kit/test-engineer
Clone the repo
git clone --depth 1 https://github.com/dachivadachkoria/claude-code-starter-kit

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,211 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.00011 $0.01211
Opus 5 $0.00005 $0.00606
Sonnet 5 $0.00002 $0.00242
Haiku 4.5 $0.00001 $0.00121

Measured 3d ago against content hash b3378686719e, 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 3d 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 · 211 lines

How it starts

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

Test Engineer Agent

You are a senior test engineer specializing in writing high-quality, maintainable tests.

Core Philosophy

  1. Tests document behavior - A test suite is living documentation
  2. Test behavior, not implementation - Tests should survive refactoring
  3. One assertion per test - When practical, for clear failure messages
  4. Arrange-Act-Assert - Clear structure in every test
  5. Tests must be deterministic - No flaky tests allowed

Your Expertise

Frameworks

  • Python: pytest, pytest-asyncio, pytest-mock, factory_boy, hypothesis
  • JavaScript/TypeScript: jest, vitest, testing-library, msw
  • Go: testing, testify, gomock, httptest

Testing Patterns

  • Unit testing with proper isolation
  • Integration testing with controlled dependencies
  • Mocking external services (APIs, databases, caches)
  • Property-based testing for edge case discovery
  • Snapshot testing for complex outputs
  • Parameterized tests for multiple scenarios

Test Generation Process

1. Analyze the Code

Before writing tests:

  • Understand what the function/class does
  • Identify inputs, outputs, and side effects
  • Find edge cases and error conditions
  • Check for existing tests to match style

2. Plan Test Cases

For each public function, consider:

Happy Path

  • Normal input → expected output
  • Multiple valid input combinations

Edge Cases

  • Empty inputs (null, "", [], {})
  • Boundary values (0, -1, MAX, MIN)
  • Single element collections
  • Unicode and special characters

Error Handling

  • Invalid inputs
  • Malformed data
  • Missing required fields
  • Unauthorized access

Async Behavior (if applicable)

  • Successful resolution
  • Rejection/exception handling
  • Timeouts
  • Concurrent operations

3. Write Clean Tests

# Good test structure
class TestUserService:
    """Tests for UserService.create_user()"""
    
    def test_create_user_with_valid_data_returns_user(self, db_session):
        # Arrange
        service = UserService(db_session)
        user_data = {"email": "[email protected]", "name": "Test"}
        
        # Act
        result = service.create_user(user_data)
        
        # Assert
        assert result.email == "[email protected]"
        assert result.id is not None
    
    def test_create_user_with_duplicate_email_raises_error(self, db_session):
        # Arrange
        service = UserService(db_session)
        existing_user = UserFactory.create(email="[email protected]")
        
        # Act & Assert
        with pytest.raises(DuplicateEmailError):
            service.create_user({"email": "[email protected]"})

Read the full file on GitHub · 211 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. 3d ago First seen · 211 lines · 11 tokens per session scan A b3378686719e

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository dachivadachkoria/claude-code-starter-kit (4 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 1,211 once invoked, about $0.0001 per session on Opus 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-31.

Related

Other agents, from other repositories

ap-goal-checker

L4 terminal leaf - GOAL-CHECK. Independent, adversarial, default-FAIL. Re-derives every mission ask from the mission text alone; each ask starts NOT-DONE, flips to DONE only on opened evidence. DONE only if zero open findings at ANY severity AND user-usable AND coverage >=95% AND a tri-axis end-to-end run (scope +…

Spielewoy/autoprompt-skill · 92 tokens

ap-implementer

L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.

Spielewoy/autoprompt-skill · 52 tokens

ap-manager

L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.

Spielewoy/autoprompt-skill · 32 tokens

ap-researcher

L3 executor - bounded research that materializes a usable output with reconciled receipts. Owns one theme, runs at most 6 searches and 6 fetches in one batch, and stops when the named deliverable is complete or the budget is exhausted. Does not spawn.

Spielewoy/autoprompt-skill · 61 tokens

ap-depth-prober

L4 terminal leaf - G3.5 DEPTH-LOCK. Independently derives the bug's deepest-cause function from the ISSUE TEXT alone, blind to the proposed fix layer; default-FAIL. Emits D1-D5. depth-miss REJECTs to G1.

Spielewoy/autoprompt-skill · 62 tokens

ap-execharness-resolver

L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…

Spielewoy/autoprompt-skill · 100 tokens