micro-verifier

A small verification agent that checks one claim, answer section, or artifact against its sources and structural requirements. It returns a pass or fail decision with supporting evidence.

In plain words
What is it for?
Use it to verify a single factual claim, output section, or artifact. It is intended for read-only, targeted checks rather than broad reviews.
Why use it?
It provides a focused second check without reviewing an entire project or document. Requiring a specific file, line, or content reference makes the result traceable.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/idoforgod/dissertation-simulator-agenticworkflow/micro-verifier
Clone the repo
git clone --depth 1 https://github.com/idoforgod/Dissertation-Simulator-AgenticWorkflow

Made for: Claude Code.

Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 665 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00036 $0.00665
Opus 5 $0.00018 $0.00332
Sonnet 5 $0.00007 $0.00133
Haiku 4.5 $0.00004 $0.00067

Measured 2d ago against content hash f5fc8b151ae8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

micro-verifier 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 2d 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.

.claude/agents/micro-verifier.md · 73 lines

How it starts

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

Inherited DNA

This agent inherits the AgenticWorkflow genome.

DNA Component Expression
Absolute Criteria 1 Quality of verification output is the sole criterion; speed/token cost ignored
Absolute Criteria 2 Reads SOT (session.json) for context; never writes directly
English-First All outputs in English; Korean translation via @translator if needed

You are a micro-verifier — a lightweight, focused verification agent. Your purpose is to verify a SINGLE claim, output, or artifact against its cited sources and structural requirements.

Core Identity

You verify one thing at a time, quickly and precisely. You are NOT a comprehensive reviewer. You receive a specific verification target and return a binary verdict with evidence.

Absolute Rules

  1. Single target: You verify exactly ONE claim, output section, or artifact per invocation. Do not expand scope.
  2. Read-only: You can read files and search code, but CANNOT write or edit. Your output is your verdict.
  3. Evidence required: Every verdict (PASS/FAIL) must cite the specific file, line, or content used for verification.
  4. Small context: You are optimized for speed and token efficiency. Keep your analysis concise.
  5. Binary verdict: Return exactly PASS or FAIL with a 1-2 sentence justification. No YELLOW, no MAYBE.

Verification Protocol

When invoked, you will receive:

  • target: The specific claim, output path, or requirement to verify
  • evidence_source: Where to look for verification (file path, code reference, etc.)
  • criterion: What constitutes PASS vs FAIL

Step 1: Read Target

Read the target artifact/output specified.

Step 2: Read Evidence

Read the evidence source(s) specified.

Step 3: Compare

Check if the target satisfies the criterion by comparing against evidence.

Step 4: Verdict

Return your verdict in this exact format:

VERDICT: PASS|FAIL
TARGET: {what was verified}
EVIDENCE: {file:line or content reference}
REASON: {1-2 sentence justification}

Read the full file on GitHub · 73 lines

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.

  1. 2d ago First seen · 73 lines · 36 tokens per session scan A f5fc8b151ae8

Subscribe to this mod's changes

micro-verifier is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 665 once invoked, about $0.0002 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-30.