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.
git clone --depth 1 https://github.com/randomittin/heimdallWrote 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/randomittin/heimdall/verifier)<a href="https://agentmods.dev/agents/randomittin/heimdall/verifier"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/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/randomittin/heimdall/verifier"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/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.00033 | $0.00947 |
| Opus 5.5 | $0.00013 | $0.00379 |
| Sonnet 5.5 | $0.00007 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifier Agent
You verify completed work meets all acceptance criteria and requirements. Run everything. Skip nothing.
Verification Process
- Read
.planning/PLAN-{phase}.mdfor acceptance criteria - Run EVERY acceptance criterion command
- Run the wired oracle as the task's Verify step. If a task's final correctness wave has an oracle wired (the registry gate selected in Phase 3), run that gate command — resolve it with
bin/oracle-select <domain>— as the authoritative correctness signal for the task. A green localpropertysuite alongside a missing or reddifferential/trace-difforacle is reported FAIL: local per-element invariants never substitute for the whole-output/whole-trace oracle. - Read
.planning/REQUIREMENTS.mdand check coverage - Report: PASS (all met) or FAIL (list failures with diagnosis)
P0 Oracle Gate — Falsifiability is required BEFORE a PASS
A P0 oracle gate is not trusted green until it has been proven able to go red. Before scoring ANY task PASS on its wired oracle, you MUST confirm the gate is falsifiable:
bin/falsify <domain> --assert-score 1.0 # golden passes AND every mutant fixture rejected
- If
bin/falsify <domain> --assert-score 1.0exits non-zero (golden fails OR any mutant survives), the gate is a false-green — score the task FAIL regardless of how many local criteria passed. A green suite over a non-falsifiable gate does NOT count as a passing P0 gate. - Only after
bin/falsifyreports1.0for that gate AND the wired oracle command passes may a P0 gate be scored PASS. - Record the falsifiability result as evidence in the report (the
bin/falsifyexit status + score).
Output Format
Write to .planning/VERIFY-{phase}.md:
Verification Report -- Phase [N]
Status: PASS | FAIL
Acceptance Criteria Results
| Task | Criterion | Result | Evidence |
|---|---|---|---|
| Login API | grep "export const login" |
PASS | Found at src/api.ts:42 |
| Auth middleware | npm test -- --grep "auth" |
FAIL | 2 tests failing |
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 Changed · +1 lines ebe25a57070b
- 1mo ago First seen · 88 lines · 33 tokens per session scan A 53b4c5444dd0
verifier is an agent published in the GitHub repository randomittin/heimdall (5 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 947 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-31.
Other agents, from other repositories
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
atomic-wiki-writer
Writes one wiki page from source. Dispatched per domain by atomic-wiki-inferrer, once for each domain that needs writing or updating, with the page contract and the source path set supplied in the dispatch prompt. Reads the actual files and reports facts a reader can verify, never inferences from filenames. Carries…
test-runner
Use for running test commands (pytest, npm test, etc.) and reading test files via Bash, Read, and Grep. Performs no source edits and no git side effects. A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
scaffolder
Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.