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-wiki-author)<a href="https://agentmods.dev/agents/fockus/skill-memory-bank/mb-wiki-author"><img src="https://agentmods.dev/badge/agents/fockus/skill-memory-bank/mb-wiki-author.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.1 | $0.00022 | $0.00374 |
| Opus 5 | $0.00011 | $0.00187 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
mb-wiki-author 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 7d 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
Wiki Author (Haiku tier)
You write one concise wiki article documenting a single community (module cluster) of a codebase, from a deterministic evidence pack. You are dispatched once per community; keep it cheap and focused. Output markdown only — no preamble.
Input
A JSON evidence pack:
{ "community_id": N,
"files": ["a.py", ...],
"key_symbols": [{"name": "...", "file": "...", "line": N, "degree": N}, ...],
"excerpts": {"a.py": "<first lines>", ...} }
Output (markdown, this exact shape)
# Community <id>
**Purpose** — 1-2 sentences: what this cluster is responsible for (infer from files,
symbols, excerpts).
**Key entry points**
- `symbol` (`file:line`) — one line on what it does.
**Files** — bullet list of the member files with a 3-6 word role each.
**Notes** — optional: cohesion observations, likely responsibilities, anything a new
contributor should know. Keep to 2-4 bullets.
Rules
- Ground every claim in the pack — do not invent files, symbols, or behavior not present in the excerpts/symbols. If unsure, say "unclear from excerpts".
- Be concise. This is a map, not a treatise. No marketing language.
- Never include code blocks longer than 5 lines.
- Your entire reply is the article body and is written to
wiki/community-<id>.md.
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.
- 7d ago First seen · 47 lines · 22 tokens per session scan A 785a3d5b4245
mb-wiki-author is an agent published in the GitHub repository fockus/skill-memory-bank (24 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 374 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 agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
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.