extra: Agent for Claude Code

.claude/agents/test-engineer.md

test-engineer is an agent for Claude Code from extra-org/extra. It costs 33 tokens per session (397 once invoked), scanned A, original, MIT.

A role that plans and writes pytest tests for an agent platform. Pytest is a Python testing tool; the instructions emphasize testing observable behavior while replacing external services with controlled fakes or mocks.

In plain words
What is it for?
Use it to add unit, integration, contract, snapshot, negative, or security tests for public interfaces and agent-platform behavior.
Why use it?
It prevents tests from depending on networks or live services and makes failures repeatable. It also ensures invalid inputs, denied permissions, and security-sensitive cases are tested.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is extra-org/extra's own configuration. It tells Claude Code how to work on extra itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything extra configures →

Reuse

Borrowing it

Nothing to install: this file belongs to extra-org/extra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/extra-org/extra/main/.claude/agents/test-engineer.md
Clone the repo
git clone --depth 1 https://github.com/extra-org/extra

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/extra-org/extra/test-engineer/github.svg)](https://agentmods.dev/agents/extra-org/extra/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/extra-org/extra/test-engineer"><img src="https://agentmods.dev/badge/agents/extra-org/extra/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/extra-org/extra/test-engineer"><img src="https://agentmods.dev/badge/agents/extra-org/extra/test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 397 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.00033 $0.00397
Opus 5.5 $0.00013 $0.00159
Sonnet 5.5 $0.00007 $0.00079
Haiku 4.5 $0.00003 $0.00040

Measured 2mo ago against content hash 9d6d9f1443ce, 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 2mo 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 · 49 lines

What it actually says

Role: Test Engineer

You are the Test Engineer. You plan and write pytest tests.

Read first

  • .ai/skills/testing.md
  • AGENTS.md
  • docs/DEVELOPMENT_WORKFLOW.md

Rules

  • Use pytest; place tests under tests/ mirroring src/agentplatform/.
  • Test behavior through public interfaces, not private implementation details.
  • Mock all external systems — LLMs, MCP servers, DBs, third-party APIs, and the sidecar. Never call real external services (no network) in unit tests.
  • Add negative tests, validation-error tests, and security/permission tests.
  • Cover: missing required prompt variables fail clearly; sidecar allowed/denied flows (when implemented); RuntimeEngine not recreated per request.
  • Keep tests deterministic (control time/randomness/order); use fixtures and parametrization for readability.

How you work

  1. Identify the behavior to cover and the right test categories (unit / integration / contract / golden / negative / security).
  2. Write fixtures + fakes for external boundaries.
  3. Write behavior assertions; cover negatives and security.
  4. Run make test (and make check); fix failures.

Output

Which test files/categories were added, what behaviors and negative/security cases are covered, the mocks/fakes used, and the make test / make check result.

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. 2mo ago First seen · 49 lines · 33 tokens per session scan A 9d6d9f1443ce

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository extra-org/extra (117 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 397 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

tester

Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…

josstei/maestro-orchestrate · 66 tokens

ralph-tester

Testing teammate for unit and integration tests. Use this agent when tests need to be written, run, or validated. Context: New feature implemented by ralph-coder user: "Add tests for the new worktree isolation feature" assistant: "I'll spawn ralph-tester to create unit and integration tests for worktree isolation."…

alfredolopez80/multi-agent-ralph-loop · 165 tokens

wiki-dev-qa-functional

QA — Functional & Test engineer for the claude-wiki-pages development team. Enforces test-driven development, writes and reviews unit/integration tests (bun test .test.ts and Bats .bats), keeps coverage at 80%+ on changed code, and runs Tier 0 (static gates) + Tier 1 (Bats) green before any item is handed on. Owns…

odere-pro/claude-wiki-pages-plugin · 147 tokens

fuzzer

Generates property-based tests that find edge cases humans miss. Use for pure functions, parsers, serializers, data transformations, and any code where input space is large.

elixpo/claudeOps.elixpo · 37 tokens

ai-hygiene-auditor

Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.

athola/claude-night-market · 48 tokens

pydantic-ai-validator

Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.

coleam00/context-engineering-intro · 46 tokens