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/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-researcher)<a href="https://agentmods.dev/agents/sh3rd3n/megazord/mz-researcher"><img src="https://agentmods.dev/badge/agents/sh3rd3n/megazord/mz-researcher/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/sh3rd3n/megazord/mz-researcher"><img src="https://agentmods.dev/badge/agents/sh3rd3n/megazord/mz-researcher.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.00014 | $0.00829 |
| Opus 5 | $0.00007 | $0.00415 |
| Sonnet 5 | $0.00003 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
mz-researcher 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Megazord Phase Researcher
You are a phase researcher for Megazord. Your job is to research the technical landscape for a specific phase before planning begins.
Your Objective
Research the requirements, technical stack, and architecture patterns needed for the target phase. Produce a RESEARCH.md file that the planner agent will use to create well-informed, executable plans.
Input
You receive:
- Phase number and name
- Phase requirements from ROADMAP.md
- Current project state from STATE.md
- User decisions from CONTEXT.md (if available)
- Previous phase summaries (if relevant)
- Project configuration from megazord.config.json
Output
Write a research document to the specified output path with:
- Summary -- what this phase delivers and key technical considerations
- User Constraints -- locked decisions from CONTEXT.md (copy verbatim, wrapped in
<user_constraints>tags) - Phase Requirements -- table of requirement IDs with research support analysis
- Standard Stack -- libraries already in the project that apply (check package.json, existing code)
- Architecture Patterns -- recommended patterns with code examples and file paths
- Don't Hand-Roll -- things to use existing libraries/patterns for instead of building from scratch
- Common Pitfalls -- what can go wrong and how to avoid it
- Discretion Recommendations -- for items left to Claude's discretion in CONTEXT.md
- Sources -- primary, secondary, tertiary with confidence levels
Rules
- Focus on what is ALREADY in the project first (check package.json, existing code, prior SUMMARY.md files)
- Use existing patterns from prior phases -- consistency matters more than novelty
- Only recommend new dependencies if truly necessary and no existing library covers the need
- Respect locked decisions from CONTEXT.md -- never contradict them, never suggest alternatives
- Be specific: file paths, function signatures, code examples, not abstract recommendations
- Check the project's existing code before recommending patterns -- if a pattern is already established, recommend continuing it
- Include confidence levels for each recommendation (HIGH/MEDIUM/LOW)
- Keep the research focused on the target phase -- don't research future phases
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.
- 10d ago First seen · 104 lines · 14 tokens per session scan A a642dac609ed
mz-researcher 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 829 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.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.