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 skills add Sh3rd3n/megazord --skill statusgit 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/skills/sh3rd3n/megazord/status)<a href="https://agentmods.dev/skills/sh3rd3n/megazord/status"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/status.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.00012 | $0.02191 |
| Opus 5 | $0.00006 | $0.01095 |
| Sonnet 5 | $0.00002 | $0.00438 |
| Haiku 4.5 | $0.00001 | $0.00219 |
Grade A, and why
status 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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mz:status
Display current project progress, phase completion, and recommended next actions. Supports compact (default) and verbose (--verbose) modes.
Reference @skills/init/design-system.md for all visual output formatting.
Reference @skills/shared/presentation-standards.md for content formatting rules.
Reference @skills/shared/terminology.md for official term definitions.
Step 1: Display Banner
╔═══════════════════════════════════════════════╗
║ ⚡ MEGAZORD ► STATUS ║
╚═══════════════════════════════════════════════╝
Step 2: Load Context
Read .planning/megazord.config.json. Extract plugin_path from the config. If plugin_path is not set, try ~/.claude/plugins/mz. If neither exists, display a warning but continue (status can still show state data without CLI tools).
If the config file does not exist, display:
╔═══════════════════════════════════════════════╗
║ ✗ No Megazord project found ║
╠═══════════════════════════════════════════════╣
║ Run /mz:init to set up your project first. ║
╚═══════════════════════════════════════════════╝
Then exit.
Read .planning/STATE.md for current position, accumulated context, and session continuity.
Read .planning/ROADMAP.md for phase listing and completion status.
Step 3: Check Verbose Flag
Check if the user's message contains --verbose or -v. Store the result as a boolean.
Step 4: Get Progress Data
Run via Bash to get progress JSON:
node {plugin_path}/bin/megazord.mjs tools progress
Parse the JSON result which contains:
overall: overall progress percentagecurrentPhase:{ completed, total }plan countsbar: pre-formatted progress bar string
Also run via Bash to get current position:
node {plugin_path}/bin/megazord.mjs tools state read-position
Parse the JSON result which contains:
phase,totalPhases,phaseNameplan,totalPlansstatus
Where {plugin_path} is resolved from config.plugin_path, falling back to ~/.claude/plugins/mz.
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 · 243 lines · 12 tokens per session scan A 06ea974fc316
status is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 2,191 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 skills, from other repositories
recipe-plan
Create work plan from design document and obtain plan approval.
Codex
Mission control: create tasks, assign to an agent/team, wait for human approval, worker runs in the background, accept results.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.