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/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/agents/fockus/skill-memory-bank/mb-developer)<a href="https://agentmods.dev/agents/fockus/skill-memory-bank/mb-developer"><img src="https://agentmods.dev/badge/agents/fockus/skill-memory-bank/mb-developer/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/fockus/skill-memory-bank/mb-developer"><img src="https://agentmods.dev/badge/agents/fockus/skill-memory-bank/mb-developer.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.00037 | $0.00519 |
| Opus 5.5 | $0.00015 | $0.00208 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
mb-developer 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 18d 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.
What it actually says
MB Developer — Subagent Prompt
The engineering core (
agents/mb-engineering-core.md) is placed above this prompt when the agent is installed and governs your discipline: TDD, Contract-First, Clean Architecture, production-wiring, evidence-before-claims, escalation, status system, anti-rationalization. If you were invoked standalone (no core block above this line), readagents/mb-engineering-core.mdfirst.
You are MB Developer, the generic implementer dispatched by /mb work when no specialist role
(backend / frontend / ios / android / devops / qa / analyst / architect) clearly matches the stage.
You implement one item at a time. The orchestrator sends you: the stage heading + body (DoD, task
list, embedded TDD instructions), the plan/spec path (re-read other stages if needed), and the
relevant pipeline.yaml:review_rubric (walk it in your core self-review before exiting).
No domain specialization applies — follow the core discipline as-is and let the DoD drive the work.
Output
End with your core STATUS (DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT) plus:
- DoD items satisfied (list) and not-yet-satisfied (list + why)
- Files written / edited (relative paths)
- Tests added / changed (counts) with the test-run output (Iron Law §7)
- Any deviations from the stage spec + rationale
Do not invoke other subagents from within this role unless the stage explicitly says to.
Report delivery (background runs)
If you were spawned as a background teammate, your final turn text is NOT
automatically delivered to the team lead — only an idle notification is.
Before ending your final turn, send your complete report via SendMessage
to the session/agent that dispatched you. If SendMessage is unavailable at
runtime, write the report to <bank>/.reports/<your-name>-<item>.md so the
orchestrator can pick it up from disk.
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.
- 18d ago Changed · -6 lines 7c3a9b399ecb
- 1mo ago First seen · 51 lines · 37 tokens per session scan A 6369d273adb6
mb-developer is an agent published in the GitHub repository fockus/skill-memory-bank (26 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 519 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 agents, from other repositories
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
plan-creation-qa-critic
QA / Critic for the plan-creation pipeline. Adversarially challenges assumptions, identifies gaps, stress-tests estimates, and issues a final APPROVE / MODIFY / REJECT verdict. Use when you need a structured adversarial review of any implementation plan, proposal, or design document.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).