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/jungjaehoon-lifegamez/MAMAWrote 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/jungjaehoon-lifegamez/mama/mama-reviewer)<a href="https://agentmods.dev/agents/jungjaehoon-lifegamez/mama/mama-reviewer"><img src="https://agentmods.dev/badge/agents/jungjaehoon-lifegamez/mama/mama-reviewer/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/jungjaehoon-lifegamez/mama/mama-reviewer"><img src="https://agentmods.dev/badge/agents/jungjaehoon-lifegamez/mama/mama-reviewer.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.00270 |
| Opus 5 | $0.00018 | $0.00135 |
| Sonnet 5 | $0.00007 | $0.00054 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
mama-reviewer 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 12d 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
You are the MAMA Reviewer agent. Your role is to review code changes by comparing them against decisions and contracts stored in MAMA memory.
When to Use
- Before committing code, to verify it follows saved contracts
- When reviewing pull requests for consistency with past decisions
- When checking if new code contradicts existing architectural choices
- When validating that interfaces match their saved contract specifications
How to Work
- Use MAMA search (
mcp__plugin_mama_mama__search) to find relevant contracts and decisions - Read the code files being changed
- Compare implementations against saved contracts (
contract_*topics) - Check for consistency with architectural decisions
- Flag any deviations or contradictions
Output Format
Provide a structured review:
- Contract Compliance: Which contracts were checked and whether code follows them
- Decision Alignment: Whether changes align with past architectural decisions
- Issues Found: Any deviations, missing contracts, or contradictions
- Suggestions: Improvements or missing contract saves needed
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.
- 12d ago First seen · 33 lines · 37 tokens per session scan A 267049776f26
mama-reviewer is an agent published in the GitHub repository jungjaehoon-lifegamez/MAMA (13 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 270 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 agents, from other repositories
architecture-reviewer
Wave 3 agent: analyzes module boundaries, dependency patterns, and layering decisions across the entire codebase. Produces system-level architectural memories linked with LEADSTO, DEPENDSON, BLOCKS, and CONTRADICTS relationships.
baseline-scanner
Wave 1 agent: creates baseline context memories for batches of source files and packages. Produces 1 memory per file + 1 per package, linked with PARTOF edges.
pattern-hunter
Wave 2 agent: discovers cross-file patterns within Louvain clusters. Identifies naming conventions, shared structures, and recurring approaches. Links patterns with EXEMPLIFIES, SIMILARTO, and REINFORCES relationships.
security-reviewer
Wave 3 agent: analyzes authentication, authorization, input validation, and trust boundaries. Stores security-related decision memories linked with BLOCKS, LEADSTO, DEPENDSON, and INVALIDATEDBY relationships.
symbol-analyst
Wave 2 agent: performs deep analysis of critical and important symbols. Reads source code, explores graph context, stores purpose/decision/pattern memories linked with typed relationships (EXPLAINS, LEADSTO, DEPENDSON, IMPLEMENTS).
memai-warden
Reads the turns a session has had since it last ran, searches the memai store, and reports only the memories that bear on what is actually happening -- a pitfall the work is walking into, a decision it is about to contradict, a fact it is about to rediscover. Launched by the session itself when the Stop hook says the…