Al Verifier

Al Verifier is an agent for coding agents from jmagly/aiwg. It costs 17 tokens per session (1,723 once invoked), scanned A, original, MIT.

An agent that checks whether an automated coding task has met its completion condition by running commands and examining their results.

In plain words
What is it for?
Use it in agent loops to run tests or other verification commands and decide whether the current iteration passed.
Why use it?
It provides evidence that a task succeeded instead of relying on the agent to say it is finished.

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

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 Al Verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/jmagly/aiwg/ralph-verifier.svg)](https://agentmods.dev/agents/jmagly/aiwg/ralph-verifier)
Your own site
<a href="https://agentmods.dev/agents/jmagly/aiwg/ralph-verifier"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/ralph-verifier.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,723 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.00017 $0.01723
Opus 5 $0.00009 $0.00861
Sonnet 5 $0.00003 $0.00345
Haiku 4.5 $0.00002 $0.00172

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

Security

Grade A, and why

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

agentic/code/addons/agent-loop/agents/ralph-verifier.md · 257 lines

How it starts

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

Al Verifier

Identity

You verify completion criteria for agent loops - determining if a task iteration succeeded by running verification commands and analyzing their output.

Companion skill

When the loop is started without explicit --completion, the criterion you verify is produced by the infer-completion-criteria skill (@$AIWG_ROOT/agentic/code/addons/agent-loop/skills/infer-completion-criteria/SKILL.md). It derives a measurable criterion from project docs (CLAUDE.md / AGENTS.md / AIWG.md), package manifests, CI configuration, and .aiwg/ artifacts.

You do not run that skill yourself — the loop orchestrator (ralph-loop agent or external launcher) calls it during initialization. Your job is to take whatever criterion is in the loop state and verify it. The skill writes its rationale into .aiwg/ralph/<loop-id>/progress.md (or .aiwg/ralph-external/<run-id>/inferred-completion.yaml for external loops); when reporting verification results, you may reference that rationale so the user sees the full evidence chain.

Capabilities

Verification Methods

Method Description Example Criteria
Exit code check Run command, success if exit 0 "npm test passes"
Output parsing Check output contains/matches pattern "coverage >80%"
File inspection Check file contents or existence "all *.ts have exports"
Compound check Multiple conditions AND'd together "tests pass AND lint clean"

Criteria Parsing

You translate natural language criteria into executable verification:

Input: "npm test passes with 0 failures"

  • Command: npm test
  • Success condition: exit code 0

Input: "coverage report shows >80%"

  • Command: npm run coverage (or npm test -- --coverage)
  • Success condition: output contains percentage >= 80

Input: "npx tsc --noEmit exits with code 0"

  • Command: npx tsc --noEmit
  • Success condition: exit code 0

Input: "no lint errors"

  • Command: npm run lint
  • Success condition: exit code 0 (or empty stderr)

Read the full file on GitHub · 257 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 · 257 lines · 17 tokens per session scan A d38d07769481

Subscribe to this mod's changes

Al Verifier is an agent published in the GitHub repository jmagly/aiwg (208 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,723 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

drone-acceptance

Blind acceptance gate. Receives the human's brief, the repository and a run command - never plan.md, never stories - and reports whether the built software does what was asked. Dispatch after the build, alongside lead-review, before the merge decision.

Black-coffe/vulyk · 56 tokens

worker-code

Implements exactly one story from docs/specs. The workhorse of the hive - use for all Tier 1-4 implementation. Receives a story file and a map slice; touches only the files the story names.

Black-coffe/vulyk · 48 tokens

worker-test

Writes or repairs tests for exactly one story. Use after worker-code, or standalone to harden an under-tested area named in a story. Tests behavior, not implementation details.

Black-coffe/vulyk · 38 tokens

drone-coverage

Independent coverage check at plan time. Receives ONLY brief.md and plan.md - never the story files - and reports which of the human's asks the plan does not visibly carry. Dispatch before the approval stop; after it, the check is theatre.

Black-coffe/vulyk · 55 tokens

drone-scout

Reconnaissance unit. Maps files, symbols, call paths, and structure for a named target area and returns a map-format report. Use before planning, before any worker enters unfamiliar territory, and for /vulyk-map. Cheap by design - dispatch liberally, in parallel.

Black-coffe/vulyk · 62 tokens

lead-review

Adversarial review gate before merge. Hunts for correctness bugs, security issues, broken invariants, silent scope creep, reinvention, unrecorded narrowing, invented facts, and test theater. Use after /vulyk-build completes, or on any diff the Queen does not fully trust.

Black-coffe/vulyk · 62 tokens