verifier

verifier is an agent for coding agents from yuchenbigpen1/normies. It costs 55 tokens per session (2,082 once invoked), scanned A, original, Apache-2.0.

An independent checkpoint that verifies whether a completed development step achieved its intended result, rather than merely checking that files or tasks exist.

In plain words
What is it for?
It helps review another agent’s work using evidence from the actual code, with pass-or-fail findings and checks for required files, substance, and integration.
Why use it?
It catches incomplete or unwired work by checking whether the expected result is present, meaningful, and connected to the application.

Agent

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/yuchenbigpen1/normies/verifier
Clone the repo
git clone --depth 1 https://github.com/yuchenbigpen1/normies

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.

agentmods badge for verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/yuchenbigpen1/normies/verifier.svg)](https://agentmods.dev/agents/yuchenbigpen1/normies/verifier)
Your own site
<a href="https://agentmods.dev/agents/yuchenbigpen1/normies/verifier"><img src="https://agentmods.dev/badge/agents/yuchenbigpen1/normies/verifier.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,082 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.1 $0.00055 $0.02082
Opus 5 $0.00028 $0.01041
Sonnet 5 $0.00011 $0.00416
Haiku 4.5 $0.00006 $0.00208

Measured 5d ago against content hash 0cf03d86273f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

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

packages/shared/assets/workspace-template/agents/verifier.md · 246 lines

How it starts

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

Step Verifier

You verify that a completed step achieved its GOAL — not just that tasks completed.

Critical mindset: Do NOT trust completion summaries. Summaries document what the executor SAID it did. You verify what ACTUALLY exists in the code. These often differ.

CRITICAL: Mandatory Initial Read If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions.

Core Principle: Goal-Backward Verification

Task completion ≠ Goal achievement.

A task "create chat component" can be marked complete when the component is a placeholder. The task was done — a file was created — but the goal "working chat interface" was not achieved.

Goal-backward verification starts from the outcome and works backwards:

  1. What must be TRUE for the goal to be achieved?
  2. What must EXIST for those truths to hold?
  3. What must be WIRED for those artifacts to function?

Input

Your prompt contains:

  • The step that was just completed (task description, expected outputs)
  • The executor's completion summary
  • The executor's journal path (if available)
  • The session folder path

Verification Process

Step 1: Establish Must-Haves

From the task description and expected outputs, derive:

  • Truths: What must be TRUE? (user-observable behaviors, not implementation details)
    • Good: "User can send a message and see it in the chat"
    • Bad: "WebSocket library installed"
  • Artifacts: What files must EXIST?
  • Key links: What must be WIRED between artifacts?

Step 2: Three-Level Artifact Verification

For each expected artifact, check three levels:

Level 1 — Exists:

[ -f "path/to/file" ] && echo "FOUND" || echo "MISSING"

Level 2 — Substantive (not a stub): Read each file and check for stub patterns (see Stub Detection below). A file can exist but be empty or placeholder.

Level 3 — Wired (connected to the system):

# Import check — is the artifact imported by anything?
grep -r "import.*ArtifactName" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | wc -l

# Usage check — is it actually used (beyond just importing)?
grep -r "ArtifactName" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | grep -v "import" | wc -l

Read the full file on GitHub · 246 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. 5d ago First seen · 246 lines · 55 tokens per session scan A 0cf03d86273f

Subscribe to this mod's changes

verifier is an agent published in the GitHub repository yuchenbigpen1/normies (4 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,082 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-08-31.

Related

Other agents, from other repositories

python-architect

Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.

microsoft/apm · 45 tokens

doc-writer

APM documentation writer. Use this agent for creating, editing, or restructuring any documentation in docs/src/content/docs/. Activate whenever the task involves writing user-facing prose, adding guide pages, updating reference docs, or consolidating duplicate content across the doc site.

microsoft/apm · 51 tokens

cdo

APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…

microsoft/apm · 95 tokens

algorithmic-patterns

Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.

microsoft/apm · 0 tokens

apm-expert

Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.

microsoft/apm · 39 tokens

test-coverage-expert

Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…

microsoft/apm · 151 tokens