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 agentmods add commands/fockus/skill-memory-bank/reviewgit clone --depth 1 https://github.com/fockus/skill-memory-bankWrote 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/fockus/skill-memory-bank/review)<a href="https://agentmods.dev/commands/fockus/skill-memory-bank/review"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/review.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.01080 |
| Opus 5 | $0.00008 | $0.00540 |
| Sonnet 5 | $0.00003 | $0.00216 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
review 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 4d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review — uncommitted code
1. Gather context
Run:
git diff --staged --name-only
git diff --name-only
git diff
git diff --staged
If ./.memory-bank/roadmap.md or ./.memory-bank/checklist.md exists, read it. That is the current work plan — compare the implementation against it.
If ./.memory-bank/codebase/ARCHITECTURE.md and ./.memory-bank/codebase/CONCERNS.md exist, read them too — ARCHITECTURE.md grounds the architectural analysis in Section 3, CONCERNS.md tells you which known-fragile areas deserve extra scrutiny when touched.
Read every changed file in full, not just the diff — you need full context for architectural analysis.
2. Principles + architecture — delegated to mb-rules-enforcer
Do NOT inline SOLID / Clean Architecture / TDD-delta checks here. Delegate to the dedicated subagent, which returns a structured JSON report + human summary:
Agent(
subagent_type="general-purpose",
model="sonnet",
description="mb-rules-enforcer: principles + architecture audit",
prompt="<contents of ~/.claude/skills/memory-bank/agents/mb-rules-enforcer.md>
files: <comma-separated list from step 1 (git diff --name-only)>
diff_range: HEAD...HEAD
rules_path: .memory-bank/RULES.md"
)
The enforcer runs scripts/mb-rules-check.sh (deterministic SRP / Clean Arch / TDD-delta) and adds LLM-level judgment for ISP / DRY. Parse its JSON for the Report in step 8 — every CRITICAL violation becomes a Critical item, every WARNING a Serious item.
Apply the remaining judgment-only checks inline:
- KISS — overcomplicated solutions, needless abstractions
- YAGNI — code written "for the future" with no present call site
These are intentionally not deterministic; the enforcer cannot replace a careful human look at "is this code simpler than it needs to be?"
3. Implementation correctness
- Does the code do what the diff/commit claims?
- Is there dead or unreachable code?
- Are there unfinished
TODO,FIXME,HACK, stubs, or placeholders? - Error handling: are all exceptional paths covered?
- Edge cases: empty values,
nil/None, empty collections, boundary numbers - Race conditions in async code
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.
- 4d ago First seen · 132 lines · 15 tokens per session scan A a273565d61f9
review is a command published in the GitHub repository fockus/skill-memory-bank (25 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,080 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.
Other commands, from other repositories
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
vitaecontext-vitaegraph
Create, validate, index, or use a private VitaeGraph.
setup
Fetch Kobiton credentials from the authenticated MCP server and write them to /.kobiton/.credentials.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
review-video
Make a " Reviews" video — a fast, faceless VO montage of REAL, verified competitor reviews that names the recurring complaints and positions YOUR business as the alternative, then hands off to your own customer testimonials.
avatar-vo-reel
Build a fullscreen voiceover-over-b-roll reel — talking-head avatar hook, then fullscreen screen-capture b-roll while the VO continues, lower-third captions, badge swap, SFX.