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 commands/sh3rd3n/megazord/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/commands/sh3rd3n/megazord/status)<a href="https://agentmods.dev/commands/sh3rd3n/megazord/status"><img src="https://agentmods.dev/badge/commands/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 | $0.00010 | $0.00030 |
| Opus 5 | $0.00005 | $0.00015 |
| Sonnet 5 | $0.00002 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
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 4d 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
Invoke the mz:status skill and follow it exactly as presented to you
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.
- 4d ago First seen · 6 lines · 10 tokens per session scan A 5cb7e86c1b69
status is a command published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 30 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 commands, from other repositories
poc
Start a hypothesis-driven POC with hard timebox. Skips 80% of the production pipeline; forces ship/pivot/kill decision at expiry.
promote
Promote a POC to MVP/production. Runs the full audits that POC-mode skipped. Required before any POC can see production.
agent-retire
Gracefully retire an LLM agent from the workforce. Archives prompt, removes from sync list, keeps verdicts for audit. Like firing a human — but reversible.
prd
Create a Product Requirements Document — conversational intake, 8-section output. Run BEFORE architect to lock WHAT and WHY before the team decides HOW.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
spec
Spec Driven Development: interview → requirements.md + design.md + tasks.md. Run before writing any code.