What is evidence-verification?

A quality-assurance method for proving that completed software work actually works. It collects evidence such as test results, coverage, build output, and deployment checks before a task is marked complete.

Use it during code reviews, task completion, agent handoffs, troubleshooting, pull-request preparation, and production deployments to verify tests, builds, coverage, and deployment results.

It prevents unsupported claims of completion and makes failures or missing checks visible. The approach is based on executable proof rather than a written assurance alone.

evidence-verification — Skill for Claude Code and Codex by ArieGoldkin

Install

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.

Any agent

npx skills add ArieGoldkin/ai-agent-hub --skill evidence-verification

Clone the repo

git clone --depth 1 https://github.com/ArieGoldkin/ai-agent-hub

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ariegoldkin/ai-agent-hub/evidence-verification/github.svg)](https://agentmods.dev/skills/ariegoldkin/ai-agent-hub/evidence-verification)

Your own site

<a href="https://agentmods.dev/skills/ariegoldkin/ai-agent-hub/evidence-verification"><img src="https://agentmods.dev/badge/skills/ariegoldkin/ai-agent-hub/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ariegoldkin/ai-agent-hub/evidence-verification"><img src="https://agentmods.dev/badge/skills/ariegoldkin/ai-agent-hub/evidence-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,119 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.03119
Opus 5	$0.00000	$0.01559
Sonnet 5	$0.00000	$0.00624
Haiku 4.5	$0.00000	$0.00312

Measured 11d ago against content hash 4e4df9975231, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 11d 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.

skills/evidence-verification/SKILL.md · 583 lines

How it starts

The opening of the file, as written. The whole thing — 583 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Evidence-Based Verification Skill

Version: 1.0.0 Type: Quality Assurance Auto-activate: Code review, task completion, production deployment

Overview

This skill teaches agents how to collect and verify evidence before marking tasks complete. Inspired by production-grade development practices, it ensures all claims are backed by executable proof: test results, coverage metrics, build success, and deployment verification.

Key Principle: Show, don't tell. No task is complete without verifiable evidence.

When to Use This Skill

Auto-Activate Triggers

Completing code implementation
Finishing code review
Marking tasks complete in Squad mode
Before agent handoff
Production deployment verification

Manual Activation

When user requests "verify this works"
Before creating pull requests
During quality assurance reviews
When troubleshooting failures

Core Concepts

1. Evidence Types

Test Evidence

Exit code (must be 0 for success)
Test suite results (passed/failed/skipped)
Coverage percentage (if available)
Test duration

Build Evidence

Build exit code (0 = success)
Compilation errors/warnings
Build artifacts created
Build duration

Deployment Evidence

Deployment status (success/failed)
Environment deployed to
Health check results
Rollback capability verified

Code Quality Evidence

Linter results (errors/warnings)
Type checker results
Security scan results
Accessibility audit results

2. Evidence Collection Protocol

## Evidence Collection Steps

1. **Identify Verification Points**
   - What needs to be proven?
   - What could go wrong?
   - What does "complete" mean?

2. **Execute Verification**
   - Run tests
   - Run build
   - Run linters
   - Check deployments

3. **Capture Results**
   - Record exit codes
   - Save output snippets
   - Note timestamps
   - Document environment

4. **Store Evidence**
   - Add to shared context
   - Reference in task completion
   - Link to artifacts

Read the full file on GitHub · 583 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

11d ago First seen · 583 lines · 0 tokens per session scan A 4e4df9975231

Subscribe to this mod's changes

evidence-verification is a skill published in the GitHub repository ArieGoldkin/ai-agent-hub (11 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,119 tokens. 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-30.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

evidence-verification