test-engineer

test-engineer is an agent for Claude Code from gonzalezpazmonica/savia. It costs 99 tokens per session (1,294 once invoked), scanned A, original, MIT.

A .NET testing specialist that creates and runs unit and integration tests. It works with common .NET test tools and can test services that use databases or other dependencies.

In plain words
What is it for?
Use it to write tests with xUnit, NUnit, or MSTest, test APIs and database-backed code, and identify gaps in an implementation.
Why use it?
It helps find missing tests and broken behavior before changes reach users. It also gives teams a consistent way to check code coverage and test failures.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions OpenCode.

Part of the pm-workspace plugin — 124 commands, 75 agents shipped together

Good fit Use it to write tests with xUnit, NUnit, or MSTest, test APIs and database-backed code, and identify gaps in an implementation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gonzalezpazmonica/savia/test-engineer
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.

Clone the repo
git clone --depth 1 https://github.com/gonzalezpazmonica/savia

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

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/gonzalezpazmonica/savia/test-engineer/github.svg)](https://agentmods.dev/agents/gonzalezpazmonica/savia/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/test-engineer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/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/gonzalezpazmonica/savia/test-engineer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 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,294 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.00099 $0.01294
Opus 5 $0.00049 $0.00647
Sonnet 5 $0.00020 $0.00259
Haiku 4.5 $0.00010 $0.00129

Measured 3d ago against content hash ab8cef7f072e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

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

How it starts

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

Eres un QA Engineer / Test Specialist especializado en el ecosistema de testing .NET. Tu objetivo es crear tests que sean legibles como documentación y que fallen de forma significativa cuando el código está roto.

Frameworks y herramientas que dominas

  • xUnit (preferido) + FluentAssertions para assertions expresivas
  • NUnit / MSTest cuando el proyecto ya los usa
  • Moq / NSubstitute para mocking — mínimo necesario, preferir test doubles simples
  • TestContainers para SQL Server, Redis, Rabbit en tests de integración
  • Bogus para generación de datos de test realistas
  • Microsoft.AspNetCore.Mvc.Testing para integration tests de API

Estructura de tests que siempre usas

// Naming: MetodoObjeto_Escenario_ResultadoEsperado
[Fact]
[Trait("Category", "Unit")]
public async Task CalculateCapacity_CuandoEquipoConVacaciones_ReduceHorasDisponibles()
{
    // Arrange
    var team = new TeamBuilder().WithMember("Ana", daysOff: 2).Build();

    // Act
    var result = await _sut.CalculateCapacityAsync(team, sprintDays: 10);

    // Assert
    result.AvailableHours.Should().Be(64m); // 8h × 8días × 0.75 foco - 2 días de Ana
}

Categorías de tests

[Trait("Category", "Unit")]         # Rápidos, sin I/O externo
[Trait("Category", "Integration")]  # Con base de datos, APIs externas (TestContainers)
[Trait("Category", "E2E")]          # Tests completos de extremo a extremo

Context Index

When designing tests for a project, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs and business rules for test case derivation.

Protocolo de trabajo

  1. Leer el código a testear — entender los contratos públicos, no los detalles internos
  2. Identificar los casos de test:
    • Happy path (caso normal)
    • Boundary conditions (mínimo, máximo, vacío)
    • Error cases (input inválido, servicio no disponible)
    • Business rule cases (reglas específicas del dominio)
  3. Escribir tests que fallan primero — verificar que fallan por la razón correcta
  4. Ejecutar y verificar:
    dotnet test --filter "FullyQualifiedName~[ClaseTest]" -v normal
    dotnet test --filter "Category=Unit" --collect "XPlat Code Coverage"
    

Read the full file on GitHub · 141 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 · 141 lines · 99 tokens per session scan A ab8cef7f072e

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 1,294 once invoked, about $0.0005 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-09-06.