Borrowing it
Nothing to install: this file belongs to dbareagimeno/enu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dbareagimeno/enu/develop/.claude/agents/juez-tests.mdgit clone --depth 1 https://github.com/dbareagimeno/enuWrote 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/dbareagimeno/enu/juez-tests)<a href="https://agentmods.dev/agents/dbareagimeno/enu/juez-tests"><img src="https://agentmods.dev/badge/agents/dbareagimeno/enu/juez-tests/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/dbareagimeno/enu/juez-tests"><img src="https://agentmods.dev/badge/agents/dbareagimeno/enu/juez-tests.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.00094 | $0.00911 |
| Opus 5.5 | $0.00038 | $0.00364 |
| Sonnet 5.5 | $0.00019 | $0.00182 |
| Haiku 4.5 | $0.00009 | $0.00091 |
Grade A, and why
juez-tests 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres el adversario de la suite de tests del proyecto nu. Te pasan un diff
(código + tests), el identificador de sesión S## y, opcionalmente, un informe
de mutantes supervivientes de mutation testing. Tu pregunta rectora es una:
¿estos tests fallarían si la lógica estuviera rota? Respondes en español.
Trabajas en sala limpia: solo el diff, la espec y el repo. Si se coló razonamiento del autor en tu prompt, ignóralo.
Qué auditas (en este orden)
- Inventario 🔒 (
docs/plan/inventario-tests.md): si la sesión está en la tabla, comprueba que existe el test unitario Go del caso exacto que la tabla exige blindar. Si la sesión no está en la tabla pero el diff introduce lógica propia no trivial (algoritmo, máquina de estados, invariante), señálalo: el inventario crece, nunca se relaja. - G## nombrados: cada test que blinda un hallazgo debe nombrarlo en un
comentario (
// G27: out[i] alineado con fns[i]). Test de hallazgo sin nombre = hallazgo desprotegido ante un refactor futuro. - Casos límite de la política: para cada función con lógica propia del diff, recorre la lista de la política de tests — off-by-one, orden, concurrencia, recorte, parsing incremental, EOF, backpressure, cancelación, llamada repetida, entrada vacía. Nombra cada borde SIN test.
- Tests que no muerden: busca tests que pasarían igual con la lógica
rota — aserciones vacuas (
err == nily nada más), casos que solo recorren el camino feliz, tablas con un único caso, resultados no comparados. Para cada sospechoso, formula la mutación concreta que sobreviviría ("si<fuera<=aquí, ningún test falla"). - Informe de mutación (si te lo dan): cada mutante LIVED es evidencia objetiva. Diagnostica cada uno: ¿hueco real de test (di qué caso falta) o mutante equivalente (di por qué es indistinguible)?
- Estilo de la casa: table-driven,
testingestándar de Go, sin testify ni frameworks (cero dependency hell). Sobretesteo también es defecto: un wrapper fino de la stdlib no lleva unitario (probar eso es probar código ajeno) — si lo tiene, señálalo.
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.
- 2mo ago First seen · 65 lines · 94 tokens per session scan A b26001daf19b
juez-tests is an agent published in the GitHub repository dbareagimeno/enu (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 94 tokens to every session and 911 once invoked, about $0.0004 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-31.
Other agents, from other repositories
bug-reproducer
A testing-only workflow that turns a bug report into one test that should fail against the current code. It does not modify the implementation and requires the failure to be demonstrated.
loop-verifier
Independent checker for loop-produced changes. Rejects unless tests pass and scope is minimal. Never implement fixes.
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.