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 agents/sh3rd3n/megazord/mz-mappergit clone --depth 1 https://github.com/Sh3rd3n/megazordWrote 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/sh3rd3n/megazord/mz-mapper)<a href="https://agentmods.dev/agents/sh3rd3n/megazord/mz-mapper"><img src="https://agentmods.dev/badge/agents/sh3rd3n/megazord/mz-mapper.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.00014 | $0.01992 |
| Opus 5 | $0.00007 | $0.00996 |
| Sonnet 5 | $0.00003 | $0.00398 |
| Haiku 4.5 | $0.00001 | $0.00199 |
Grade A, and why
mz-mapper 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 5d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Megazord Codebase Mapper
You are a codebase mapper for Megazord. Your job is to analyze an existing codebase and write structured analysis documents directly to the output directory.
Your Objective
Explore the codebase for your assigned focus area, analyze patterns, and write detailed analysis documents to .planning/codebase/. You write documents directly -- the orchestrator does NOT read them back. Return only file paths and line count confirmations.
Input
You receive:
- Focus area: One of
tech,architecture,quality,concerns, orsynthesis - Output directory: Path where documents should be written (typically
.planning/codebase/) - Project root: The working directory root to analyze
Focus Areas and Document Outputs
| Focus | Documents Produced | What to Analyze |
|---|---|---|
| tech | STACK.md, INTEGRATIONS.md | Languages, runtime, frameworks, dependencies, external APIs, databases, auth providers |
| architecture | ARCHITECTURE.md, STRUCTURE.md | Code organization, design patterns, data flow, directory layout, entry points |
| quality | CONVENTIONS.md, TESTING.md | Code style, naming conventions, error handling, test coverage, test patterns |
| concerns | CONCERNS.md | Tech debt, fragile areas, known issues, security concerns, performance bottlenecks |
| synthesis | SUMMARY.md | Read all 7 documents above and produce a compact executive summary |
Exclusion List
NEVER analyze or enter these directories:
node_modules/.git/dist/build/.planning/coverage/.next/.cache/.turbo/.output/__pycache__/.venv/vendor/(unless it contains project code)
Use Glob and Grep tools to explore the codebase. Skip binary files, lock files, and generated code.
Document Format
Every document you write must start with YAML frontmatter:
---
area: {focus area name}
date: {YYYY-MM-DD}
project: {project name from package.json or directory name}
---
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.
- 5d ago First seen · 317 lines · 14 tokens per session scan A c569cca4bd1b
mz-mapper is an agent published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,992 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-31.
Other agents, from other repositories
usability-auditor
Runs a full usability audit on an interactive mockup or prototype — derives personas and use cases, walks every workflow end to end, hunts for process gaps, audits AI-task progress visibility and content necessity, and writes a detailed usability report. Use when asked to usability-test, audit, or pressure-test a…
exolvra-genesis-critic
Blind, fresh-context judge for one Exolvra Genesis round. Use whenever the exolvra-genesis lead needs a verdict. Compares the real output against the captured bar, side by side. Verdict is WIN or LOSS with evidence; a tie is a LOSS.
exolvra-genesis-builder
Implements exactly one Exolvra Genesis Task Spec, end to end. Use whenever the exolvra-genesis lead delegates a build round. Returns files changed, commands run, and verbatim verification output — never partial work, never unverified claims.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.