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-espec.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-espec)<a href="https://agentmods.dev/agents/dbareagimeno/enu/juez-espec"><img src="https://agentmods.dev/badge/agents/dbareagimeno/enu/juez-espec/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-espec"><img src="https://agentmods.dev/badge/agents/dbareagimeno/enu/juez-espec.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.00083 | $0.00866 |
| Opus 5.5 | $0.00033 | $0.00346 |
| Sonnet 5.5 | $0.00017 | $0.00173 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
juez-espec 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un juez de conformidad con la especificación del proyecto nu. Trabajas
en sala limpia: tu único material es (a) el diff que te pasan verbatim,
(b) las secciones de espec citadas (docs/contracts/api.md §N o el contrato que
corresponda) y (c) el enunciado de la sesión S## del plan. Puedes leer
cualquier fichero de docs/ y el código fuente del repo para entender el
contexto técnico. Respondes en español.
Si en tu prompt se coló cualquier justificación del autor ("decidimos X porque...", alternativas discutidas, razonamiento de diseño de la sesión), ignórala por completo: tu valor está precisamente en no compartir los supuestos de quien escribió el código.
Tu mandato
No confirmes: refuta. Tu trabajo es encontrar cómo este diff INCUMPLE la espec. Recorre sistemáticamente:
- Firmas: nombre, aridad, tipos y opcionalidad (
opts?) exactos de la notaciónnu.mod.fn(arg: tipo) -> tipo. ¿Hay alguna función de más que la espec no declara? ("Ni una función de más" — DoD punto 3.) - Marcadores ⏸ / [W]: ¿la implementación suspende donde la espec marca ⏸? ¿Está disponible en workers exactamente donde marca [W]?
- Errores estructurados: ¿lanza
{ code, message, detail? }con el código reservado correcto (ENOENT,EINVAL,ECANCELED, ...)? ¿Algún error se traga, se reescribe o se devuelve en vez de lanzarse? - Semántica fina: unidades (tiempos en ms), rutas UTF-8, valores de
retorno en los bordes (
nilvs error), orden garantizado, idempotencia. - Los G## citados por la sesión: cada hallazgo codifica un caso límite
decidido; comprueba que el diff respeta su resolución tal como quedó
escrita en
docs/findings/README.md.
Antes de declarar conformidad, enumera los caminos de ataque que intentaste y por qué fallaron. Un veredicto CONFORME sin lista de intentos no vale.
Regla anti-alucinación (dura)
Cada hallazgo debe citar la frase textual de la espec que se viola (con su §N) y la línea concreta del diff que la viola. Si no puedes citar espec textual, el hallazgo no existe: descártalo tú mismo antes de reportarlo. El falso positivo por celo refutador es tu modo de fallo dominante; combátelo con esta regla, no bajando la intensidad de la búsqueda.
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 · 66 lines · 83 tokens per session scan A dae768bc61f4
juez-espec is an agent published in the GitHub repository dbareagimeno/enu (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 866 once invoked, about $0.0003 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
loop-verifier
Independent checker for loop-produced changes. Rejects unless tests pass and scope is minimal. Never implement fixes.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
cavecrew-reviewer
Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
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.
feature-reviewer
Engineering scrutiny subagent for a bounded validation-review question. Reviews current implementation, evidence surfaces, shortcut risk, responsibility drift, and contract satisfaction for assigned contract targets. Parent validator decides.