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/lifecyclegit 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/lifecycle)<a href="https://agentmods.dev/commands/sh3rd3n/megazord/lifecycle"><img src="https://agentmods.dev/badge/commands/sh3rd3n/megazord/lifecycle.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.00011 | $0.00031 |
| Opus 5 | $0.00005 | $0.00015 |
| Sonnet 5 | $0.00002 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
lifecycle 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 3d 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:lifecycle 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.
- 3d ago First seen · 6 lines · 0 tokens per session scan A cd68f23244ac
lifecycle is a command published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 31 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
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
release
Cut a release — bump all workspace versions in sync, generate/update CHANGELOG.md from Conventional Commits, commit and tag (push gated on confirmation).
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
changelog
Create engaging changelogs for recent merges to main branch.
release
Release a new version. Bumps version, updates docs/site/changelog, tags, pushes, and updates the marketplace repo.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.