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.
npx skills add Kaddo-kdd/kaddo --skill evidence-verificationgit clone --depth 1 https://github.com/Kaddo-kdd/kaddoWrote 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/skills/kaddo-kdd/kaddo/evidence-verification)<a href="https://agentmods.dev/skills/kaddo-kdd/kaddo/evidence-verification"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/evidence-verification/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/skills/kaddo-kdd/kaddo/evidence-verification"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/evidence-verification.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.00422 |
| Opus 5.5 | $0.00025 | $0.00169 |
| Sonnet 5.5 | $0.00013 | $0.00084 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
evidence-verification 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 1mo 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.
What it actually says
Evidence Verification Skill
Purpose
Estandarizar la recolección de evidencia de implementación y la verificación de Criterios de Aceptación antes de completar un Work Item.
When to use
Después de que la implementación y las pruebas de un Work Item terminan, antes de llamar
kaddo learn.
Inputs
- El Work Item (id, ACs, affected_modules, release_gates, completion_exceptions).
- El diff o lista de archivos modificados.
- Resultados de pruebas y validaciones.
- Excepciones propuestas con categoría e impacto.
Output
Un reporte de verificación: estado por AC, release gates, excepciones, desviaciones planned vs actual, y decisión de completitud (READY_TO_COMPLETE | NEEDS_WORK | BLOCKED | READY_WITH_EXCEPTIONS).
Rules
- Nunca marcar un AC como passed sin evidencia concreta.
- Nunca omitir un release gate fallido sin registrar una excepción aceptada.
- No incluir rutas de secretos en changed_paths.
- Usar
kaddo verifyo MCP toolskaddo_collect_evidence/kaddo_verify_work_item.
Quality checklist
- Cada AC tiene un status explícito.
- Los release gates fallidos tienen blocker documentado.
- Las excepciones aceptadas tienen approved_by y razón.
- No hay rutas de secretos en la evidencia.
- La decisión de completitud es coherente con ACs y gates.
Example output
Un reporte de verificación con ACs, gates, excepciones y decisión de completitud.
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.
- 1mo ago First seen · 50 lines · 63 tokens per session scan A 36344bdd1595
evidence-verification is a skill published in the GitHub repository Kaddo-kdd/kaddo (67 stars, last pushed 13d ago), licensed MIT. It adds 63 tokens to every session and 422 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-09-29.
Other skills, from other repositories
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.