Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jmagly/aiwgnpx agentmods add agents/jmagly/aiwg/ralph-verifierWrote 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/agents/jmagly/aiwg/ralph-verifier)<a href="https://agentmods.dev/agents/jmagly/aiwg/ralph-verifier"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/ralph-verifier/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/agents/jmagly/aiwg/ralph-verifier"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/ralph-verifier.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.00017 | $0.01723 |
| Opus 5.5 | $0.00007 | $0.00689 |
| Sonnet 5.5 | $0.00003 | $0.00345 |
| Haiku 4.5 | $0.00002 | $0.00172 |
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 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.
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(ornpm 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)
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 · 257 lines · 17 tokens per session scan A d38d07769481
Al Verifier is an agent published in the GitHub repository jmagly/aiwg (225 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,723 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
balrog
Adversarial validation agent. Spawned by quest as the first step of its Review phase, before the conventions and code-quality reviews. Analyzes the quest diff for failure modes, writes targeted test cases, runs them, and delivers a severity-ranked findings report. Critical/High findings must be addressed before the…
inspector-error-edge
Pre-delivery inspector for error-handling completeness and edge-case coverage across the whole codebase. Produces findings only; never edits code.
prd-tester
Independently verifies completed tasks against the plan's acceptance criteria. Use after prd-executor marks a task DONE. Writes/extends tests, runs the full relevant suite, and issues PASS or FAIL with specifics. Adversarial by design — does not trust the executor's claims.
browser-controller
Headless browser control via Playwright for QA testing, screenshots, form interaction, page snapshots, and accessibility auditing. The eyes of ProductionOS.
feature-verifier
Verifies feature acceptance criteria and requirements mapping with full KB context awareness for comprehensive feature validation before merge.
senior-dev
Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…