A verification workflow that checks a finished task against its acceptance criteria and records evidence for the result.

Use it to review a task, produce reproducible evidence, and report a pass, fail, or partial result with follow-up items.

It reduces the risk of marking work complete without testing whether it actually meets the agreed requirements.

mb-verify — Skill for Claude Code and Codex by mrvladd-d

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.

Any agent

npx skills add mrvladd-d/memobank --skill mb-verify

Clone the repo

git clone --depth 1 https://github.com/mrvladd-d/memobank

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mrvladd-d/memobank/mb-verify.svg)](https://agentmods.dev/skills/mrvladd-d/memobank/mb-verify)

Your own site

<a href="https://agentmods.dev/skills/mrvladd-d/memobank/mb-verify"><img src="https://agentmods.dev/badge/skills/mrvladd-d/memobank/mb-verify.svg" alt="Measured on agentmods" height="20"></a>

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,046 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.02046
Opus 5	$0.00009	$0.01023
Sonnet 5	$0.00003	$0.00409
Haiku 4.5	$0.00002	$0.00205

Measured 8d ago against content hash 02636a3e8ceb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

mb-verify 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 8d 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.

skills/mb-verify/SKILL.md · 158 lines

How it starts

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

mb-verify — Verifier loop (acceptance → evidence → verdict)

What it does: checks a completed task against acceptance criteria and records the result with evidence.
Use it when: implementation is done and you want an explicit PASS, FAIL, or partial verdict.
Input: TASK_ID, acceptance criteria sources, and the task protocol files.
Output: verification.md, evidence artifacts, verification verdict, and recommended next status/follow-up bugs when criteria fail.

Goal

Independent-ish verification so we don’t “trust without verify”.

This is not the adversarial semantic pass. If a task may satisfy AC/REQ while still being wrong in substance, follow with /red-verify / mb-red-verify.

Status Transition Modes

Status transitions have two modes.

Scheduler mode:

/autopilot and /autonomous own task status transitions.
Scheduler decides closure/failure/blocking eligibility.
/execute returns scoped implementation handoff; it does not close tasks.
/verify gives functional verdict/evidence; in scheduler mode it does not close/fail/block/promote.
/red-verify gives semantic verdict for T2/T3; in scheduler mode it does not close/fail/block/promote.
/mb-sync records/reconciles state after the scheduler-provided closure/failure/blocking decision. It does not decide closure itself.
T0/T1 scheduler closure may use compact evidence / functional PASS according to tier policy.
T2/T3 scheduler closure requires VERDICT: PASS plus SEMANTIC_VERDICT: semantic-pass before scheduler marks done.
T3 scheduler closure also requires exact markers HUMAN_CHECKPOINT: done and ROLLBACK_RECOVERY_NOTE: present.

Manual mode:

Expected T0/T1 simple flow: /execute -> /verify.
Manual closure is allowed only when an explicit closure owner exists.
T0/T1 may be marked done after functional VERDICT: PASS and completed evidence.
T2/T3 must not treat /verify PASS alone as final done; run /red-verify and require SEMANTIC_VERDICT: semantic-pass before final closure//mb-sync.
If required T2/T3 /red-verify returns anything other than semantic-pass, leave closure pending or blocked, not done; optional T0/T1 red-verify does not make their normal verify-based closure stricter.
semantic-concern in manual mode means do not trust the existing done state without human review / follow-up.
Do not mix scheduler mode and manual mode inside one task run.
No persisted mode field is used.

Read the full file on GitHub · 158 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/verifier.md 1.3 KB

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.

8d ago First seen · 158 lines · 17 tokens per session scan A 02636a3e8ceb

Subscribe to this mod's changes

mb-verify is a skill published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 2,046 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

mb-verify