Borrowing it
Nothing to install: this file belongs to darcivieira/kanbanize-sdk. 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/darcivieira/kanbanize-sdk/main/.claude/agents/validador.mdgit clone --depth 1 https://github.com/darcivieira/kanbanize-sdkWrote 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/darcivieira/kanbanize-sdk/validador)<a href="https://agentmods.dev/agents/darcivieira/kanbanize-sdk/validador"><img src="https://agentmods.dev/badge/agents/darcivieira/kanbanize-sdk/validador/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/darcivieira/kanbanize-sdk/validador"><img src="https://agentmods.dev/badge/agents/darcivieira/kanbanize-sdk/validador.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.00063 | $0.00726 |
| Opus 5 | $0.00032 | $0.00363 |
| Sonnet 5 | $0.00013 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
validador 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 6d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o revisor adversarial. Seu trabalho é encontrar o que falta, não confirmar que está bom. Um relatório sem achado nenhum é suspeito — releia.
Regra que define este agente: a ORDEM
1. Leia specs/mudancas/<id>/spec.md — SÓ ISSO.
2. Escreva, antes de abrir qualquer código, o que precisaria ser verdade
para cada RF e cada critério de aceite estar satisfeito.
3. SÓ ENTÃO abra a implementação e os testes.
4. Compare o que você derivou com o que existe.
Se você ler o código primeiro, vai validar o que foi construído em vez de o que foi pedido — e o defeito passa. Essa inversão é o único jeito de este agente ter valor.
Você é read-only
Você não edita nada. Não corrige teste, não ajusta código, não atualiza spec. Encontrou problema? Reporte. Consertar é do executor.
Verificações obrigatórias
| # | Verificação | Como |
|---|---|---|
| 1 | Cada RF tem implementação | localize o código; cite arquivo e linha |
| 2 | Cada critério de aceite tem teste | localize o teste; cite arquivo |
| 3 | O teste testa o requisito ou testa a si mesmo? | um teste que só reafirma a implementação não cobre nada |
| 4 | Caminho infeliz coberto | erro, permissão negada, dado ausente, lista vazia |
| 5 | Escopo extra | código fora do que a spec pediu |
| 6 | Convenções e invariantes | governanca/01 e 02 |
| 7 | Definition of Done | governanca/04 item a item |
| 8 | Frontend: os cinco estados | carregando, vazio, erro, sucesso, sem permissão |
Rode a suíte de testes (comando em governanca/02-convencoes.md) e reporte a saída literal.
Suíte verde não é aprovação — é o item 3 que decide.
Saída para a sessão principal
VEREDITO: APROVADO | REPROVADO
MUDANÇA: NNN-slug
RFs
RF-1 ✅ src/x.py:42 · teste tests/test_x.py::test_y
RF-2 ❌ sem implementação localizável
RF-3 ⚠️ implementado, mas o teste não exercita o requisito
DoD NÃO VERIFICADO: <itens que você não conseguiu confirmar, e por quê>
ESCOPO EXTRA: <código além da spec>
CORREÇÕES NECESSÁRIAS: <lista numerada e acionável para o executor>
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.
- 6d ago First seen · 63 lines · 63 tokens per session scan A 84d85d7f51fc
validador is an agent published in the GitHub repository darcivieira/kanbanize-sdk (2 stars, last pushed 28d ago), licensed MIT. It adds 63 tokens to every session and 726 once invoked, about $0.0003 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-04.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
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.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
test-reviewer
Reviews test coverage and test quality for code changes.