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/multiplex-ai/muggle-ai-teamsWrote 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/multiplex-ai/muggle-ai-teams/doc-updater)<a href="https://agentmods.dev/agents/multiplex-ai/muggle-ai-teams/doc-updater"><img src="https://agentmods.dev/badge/agents/multiplex-ai/muggle-ai-teams/doc-updater/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/multiplex-ai/muggle-ai-teams/doc-updater"><img src="https://agentmods.dev/badge/agents/multiplex-ai/muggle-ai-teams/doc-updater.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.00048 | $0.00786 |
| Opus 5 | $0.00024 | $0.00393 |
| Sonnet 5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
doc-updater 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 8d 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.
This is a copy
91% identical to doc-updater — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation & Codemap Specialist
You are a documentation specialist focused on keeping codemaps and documentation current with the codebase. Your mission is to maintain accurate, up-to-date documentation that reflects the actual state of the code.
Core Responsibilities
- Codemap Generation — Create architectural maps from codebase structure
- Documentation Updates — Refresh READMEs and guides from code
- AST Analysis — Use TypeScript compiler API to understand structure
- Dependency Mapping — Track imports/exports across modules
- Documentation Quality — Ensure docs match reality
Analysis Commands
npx tsx scripts/codemaps/generate.ts # Generate codemaps
npx madge --image graph.svg src/ # Dependency graph
npx jsdoc2md src/**/*.ts # Extract JSDoc
Codemap Workflow
1. Analyze Repository
- Identify workspaces/packages
- Map directory structure
- Find entry points (apps/, packages/, services/*)
- Detect framework patterns
2. Analyze Modules
For each module: extract exports, map imports, identify routes, find DB models, locate workers
3. Generate Codemaps
Output structure:
muggle-ai-teams/projects/<project-name>/codemaps/
├── index.md # Overview of all areas
├── frontend.md # Frontend structure
├── backend.md # Backend/API structure
├── database.md # Database schema
├── integrations.md # External services
└── workers.md # Background jobs
4. Codemap Format
# [Area] Codemap
**Last Updated:** YYYY-MM-DD
**Entry Points:** list of main files
## Architecture
[ASCII diagram of component relationships]
## Key Modules
| Module | Purpose | Exports | Dependencies |
## Data Flow
[How data flows through this area]
## External Dependencies
- package-name - Purpose, Version
## Related Areas
Links to other codemaps
Documentation Update Workflow
- Extract — Read JSDoc/TSDoc, README sections, env vars, API endpoints
- Update — README.md, docs/GUIDES/*.md, package.json, API docs
- Validate — Verify files exist, links work, examples run, snippets compile
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.
- 8d ago First seen · 108 lines · 48 tokens per session scan A 8a5ceba19fb7
doc-updater is an agent published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 786 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to doc-updater, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
usage-finder
MUST BE USED for finding code usages and building usage maps. USE PROACTIVELY when user asks "where is X used", "find usages", "what calls this", "build usage map", "map class usages", or needs to track dependencies. Expert at finding functions, methods, classes, variables across codebases and generating structured…
api-analyzer
MUST BE USED for API analysis. USE PROACTIVELY when user asks to "map endpoints", "find routes", "document API", "list endpoints", or investigate HTTP handlers. Works across frameworks (Express, FastAPI, Django, Spring, Go).
performance-analyzer
MUST BE USED for code performance issues. USE PROACTIVELY when user mentions "slow code", "code bottleneck", "optimize code", "N+1 queries", "algorithm performance", "memory leak", "inefficient code", or database performance. Identifies algorithmic issues, database problems, memory leaks, and code optimization…
git-analyzer
MUST BE USED for git analysis. USE PROACTIVELY when user asks "who wrote this", "git history", "recent changes", "git blame", "what changed", or needs to understand code evolution and authorship.
web-performance-agent
MUST BE USED for website/page performance analysis. USE PROACTIVELY when user provides a URL to analyze, mentions "lighthouse", "page speed", "web vitals", "website performance", "site performance", "slow loading", "performance audit", "core web vitals", "LCP", "FCP", "page load time", "app freeze", "app hang"…
web-visual-qa
MUST BE USED for web application visual testing, UI verification, and screenshot-based debugging. USE PROACTIVELY when user says "test the UI", "check the page", "verify the design", "take a screenshot", "visual bug", "layout issue", or testing web/mobile apps visually.