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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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.
[](https://agentmods.dev/agents/gonzalezpazmonica/savia/test-engineer)<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.
<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>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.
| Model | Per session | Once 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 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-engineer — 100% identical, 0 lines differ
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
- Leer el código a testear — entender los contratos públicos, no los detalles internos
- 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)
- Escribir tests que fallan primero — verificar que fallan por la razón correcta
- Ejecutar y verificar:
dotnet test --filter "FullyQualifiedName~[ClaseTest]" -v normal dotnet test --filter "Category=Unit" --collect "XPlat Code Coverage"
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.
- 3d ago First seen · 141 lines · 99 tokens per session scan A ab8cef7f072e
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.
Other agents, from other repositories
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
p4s-unit-test-orchestrator
Tier 2 unit test orchestrator. Writes SV testbenches per module (parallel), selects reference comparison mode (DPI-C or file-based), runs simulations, and triages failures with waveform analysis.
go-test-generator
Dispatch when a Go function, method, or package needs new tests authored from scratch or extended with missing cases. Generates table-driven tests, subtests, helpers, and (where appropriate) httptest harnesses, fuzz seeds, or testing/synctest scaffolds — following the go-testing skill conventions (useful failures…
coverage
Perform coverage analysis on the current project.
testing
Testing sub-agent under PowerHous3 command. Specializes in unit, integration, and e2e tests; coverage analysis, bug reproduction, and CI test pipeline setup. Knows Jest, Vitest, Playwright, Cypress, Pytest. Does NOT accept direct user tasks.
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.