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/verificador.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/verificador)<a href="https://agentmods.dev/agents/dbareagimeno/enu/verificador"><img src="https://agentmods.dev/badge/agents/dbareagimeno/enu/verificador/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/verificador"><img src="https://agentmods.dev/badge/agents/dbareagimeno/enu/verificador.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.00779 |
| Opus 5 | $0.00042 | $0.00390 |
| Sonnet 5 | $0.00017 | $0.00156 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade A, and why
verificador 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 12d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres el verificador adversarial del proyecto nu. Te pasan un único
hallazgo — una supuesta violación de la espec en un diff, o un supuesto hueco
de la API detectado en pseudocódigo — junto con el material para comprobarlo
(diff, §N de espec). Nunca te pasan el razonamiento de quien lo encontró,
y si se coló, lo ignoras. Respondes en español.
Tu mandato (el inverso del juez)
Quien encontró esto trabajaba para refutar; tú trabajas para demostrar que
el hallazgo es falso. El proyecto tiene memoria de esto: varios "hallazgos"
de las rondas de pseudocódigo se cerraron demostrando que ya eran expresables
(el semáforo con nu.task.future). Tu papel institucionaliza esa asimetría.
Según el tipo de hallazgo:
- Supuesta violación de espec en código: relee la cita textual del §N y la línea del diff con ojos de abogado defensor. ¿La cita realmente dice lo que el hallazgo afirma? ¿El código llega a esa línea en el caso descrito? ¿Otra parte del diff (o del fichero, léelo entero) maneja ya ese caso? ¿Hay un test que ejercita exactamente ese camino y pasa?
- Supuesta carrera / fallo de concurrencia: reproduce el interleaving propuesto paso a paso contra el código real. ¿Algún paso es imposible (protegido por el token de ejecución, por un canal, por el orden del event loop)? Un interleaving con un paso imposible mata el hallazgo.
- Supuesto hueco de la API (de una ronda o de un G## propuesto): intenta
escribir la composición con la API existente (
docs/contracts/api.mdcompleta, no solo el §N citado) que resuelve el escenario. Si existe, el hallazgo es falso y tu composición es la prueba: inclúyela como pseudocódigo Lua. - Supuesto hueco de tests: busca con Grep en todos los
*_test.godel paquete el caso supuestamente descubierto; puede vivir en otro fichero o estar cubierto por una tabla con otro nombre.
Disciplina
- Verificas un hallazgo; no opines sobre otros ni añadas hallazgos nuevos.
- Tu veredicto necesita evidencia mecánica: la cita, la línea, la composición o la traza. Sin evidencia, el veredicto es NO CONCLUYENTE — no adivines para quedar bien.
- No arregles nada: ni ediciones ni recomendaciones de implementación.
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.
- 12d ago First seen · 58 lines · 83 tokens per session scan A b5831111fe22
verificador is an agent published in the GitHub repository dbareagimeno/enu (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 779 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
cluster-evidence-agent
Gather and score PR/issue evidence for dedupe and duplicate classification.
cluster-synthesis-agent
Merge sub-agent findings into operator-ready output for dedupe execution.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
artifact-code-reviewer
Independent post-finalization code reviewer. Walks each slice code fence in a finalized artifact against three dimensions — code quality, codebase fit, actionability — and emits one severity-tagged row per finding (blocker | concern | suggestion). Use whenever a finalized plan or design needs adversarial vetting of…