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/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/commands/mrvladd-d/memobank/red-verify)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/red-verify"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/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/commands/mrvladd-d/memobank/red-verify"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/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.00028 | $0.02503 |
| Opus 5.5 | $0.00011 | $0.01001 |
| Sonnet 5.5 | $0.00006 | $0.00501 |
| Haiku 4.5 | $0.00003 | $0.00250 |
Grade A, and why
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 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/red-verify — Adversarial semantic verification
Этот проход должен ловить ситуации:
- acceptance criteria формально выполнены, но решена не та проблема
- локально всё выглядит корректно, но решение вредит системе целиком
- реализация переоптимизирована под локальную task interpretation и игнорирует соседние ограничения
- появляются drift, state inconsistency, operational risks или скрытая стоимость сопровождения
Разделение ролей:
/verify→ "выполнено ли по AC/REQ и есть ли evidence?"/review→ "достаточно ли качественен сам Memory Bank / planning surface?"/red-verify→ "это вообще хорошее и правильное решение в substance?"- scheduler (
/autopilot//autonomous) → task status transitions, closure, failure handling, and dependent block/unblock in scheduler mode
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 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 · 186 lines · 28 tokens per session scan A 0700ae87083c
red-verify is a command published in the GitHub repository mrvladd-d/memobank (56 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 2,503 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 commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.