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.
npx skills add mrvladd-d/memobank --skill mb-red-verifygit clone --depth 1 https://github.com/mrvladd-d/memobankWrote 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/skills/mrvladd-d/memobank/mb-red-verify)<a href="https://agentmods.dev/skills/mrvladd-d/memobank/mb-red-verify"><img src="https://agentmods.dev/badge/skills/mrvladd-d/memobank/mb-red-verify/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/skills/mrvladd-d/memobank/mb-red-verify"><img src="https://agentmods.dev/badge/skills/mrvladd-d/memobank/mb-red-verify.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.00030 | $0.02150 |
| Opus 5 | $0.00015 | $0.01075 |
| Sonnet 5 | $0.00006 | $0.00430 |
| Haiku 4.5 | $0.00003 | $0.00215 |
Grade A, and why
mb-red-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 10d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mb-red-verify — Adversarial semantic verification
- What it does: pressure-tests one completed
TASK-*for semantic correctness, hidden failure modes, and systemic harm. - Use it when: a task may be locally correct yet still wrong in product/domain/architectural/operational reality.
- Input:
TASK_ID, task intent, actual change surface, tests/evidence, and only then relevant spec reconciliation. - Output:
red-verification.md, a concise semantic-risk report, and follow-up bugs/tasks when concerns are serious.
Goal
Catch changes that are "disciplined but wrong":
- pass acceptance criteria but solve the wrong problem
- work locally but damage system integrity
- overfit to the task record and ignore neighboring constraints
- introduce architectural drift, state inconsistency, or hidden maintenance cost
- create false confidence because the evidence surface is too narrow
This is intentionally different from existing commands
mb-verifychecks acceptance criteria and evidence-backed task completion.mb-reviewreviews Memory Bank quality, planning, and discipline in fresh context.mb-red-verifyasks: "Is this solution actually right in substance?"
Status Transition Modes
Status transitions have two modes.
Scheduler mode:
/autopilotand/autonomousown task status transitions.- Scheduler decides closure/failure/blocking eligibility.
/executereturns scoped implementation handoff; it does not close tasks./verifygives functional verdict/evidence; in scheduler mode it does not close/fail/block/promote./red-verifygives semantic verdict for T2/T3; in scheduler mode it does not close/fail/block/promote.- Scheduler must write the closure/failure/blocking decision, final task status, and evidence links to the authoritative indexed
.memory-bank/tasks/TASK-*.task.jsonrecord before/mb-sync. /mb-syncrecords/reconciles already-written task state. It does not decide closure/failure/blocking/promotion and must not sync a decision that exists only in scheduler context.- T0/T1 scheduler closure may use compact evidence / functional PASS according to tier policy.
- T2/T3 scheduler closure requires
VERDICT: PASSplusSEMANTIC_VERDICT: semantic-passbefore scheduler marksdone. - T3 scheduler closure also requires exact markers
HUMAN_CHECKPOINT: doneandROLLBACK_RECOVERY_NOTE: present.
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.
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.
- 10d ago First seen · 171 lines · 30 tokens per session scan A 586c9c18d4fe
mb-red-verify is a skill published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 2,150 once invoked, about $0.0002 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.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.