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 skills/sh3rd3n/megazord/helpnpx skills add Sh3rd3n/megazord --skill helpgit 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/help)<a href="https://agentmods.dev/skills/sh3rd3n/megazord/help"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/help.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.00014 | $0.00945 |
| Opus 5 | $0.00007 | $0.00473 |
| Sonnet 5 | $0.00003 | $0.00189 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
help 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Megazord Help
Display the complete skill reference for Megazord.
Reference @skills/init/design-system.md for visual output formatting.
Reference @skills/shared/terminology.md for official term definitions.
Display the stage banner:
+===============================================+
| MEGAZORD > HELP |
+===============================================+
Available Skills
| Skill | Description | Status |
|---|---|---|
/mz:help |
Show this help listing | Available |
/mz:init |
Initialize project with config and planning structure | Available |
/mz:settings |
View and modify project configuration | Available |
/mz:plan |
Plan a phase into tasks with dependencies | Available |
/mz:status |
Show project progress and next actions | Available |
/mz:pause |
Save context for session handoff | Available |
/mz:resume |
Restore context from previous session | Available |
/mz:quick |
Run a quick task without project ceremony | Available |
/mz:go |
Execute the current phase plan (subagent or Agent Teams mode) | Available |
/mz:review |
Two-stage code review (spec + quality) | Available |
/mz:verify |
Verify phase deliverables match criteria | Available |
/mz:debug |
Systematic four-phase debugging | Available |
/mz:discuss |
Socratic brainstorming before implementation | Available |
/mz:map |
Analyze existing codebase for brownfield support | Available |
/mz:lifecycle |
Complete milestone lifecycle (audit, archive, next version) | Available |
Usage
Run any skill by typing its name as a slash command:
/mz:help Show this listing
/mz:init Initialize a new Megazord project
/mz:settings View or modify project configuration
/mz:plan Plan the next phase into tasks
/mz:status Check project progress
/mz:status -v Detailed progress with all phases and metrics
/mz:pause Save session for later
/mz:resume Restore and continue from last session
/mz:quick {task} Run a quick task inline
/mz:go Execute the current phase plan
/mz:go --dry-run Preview execution plan without running
/mz:go --from 2 Start from plan 2, skip earlier plans
/mz:go --tasks 1,3 Execute only specific plans
/mz:go --teams Force Agent Teams mode (requires experimental flag)
/mz:go --no-teams Force subagent mode (skip Agent Teams)
/mz:review Review the latest commit
/mz:review --plan 05-01 Review all changes from a plan
/mz:review --files src/lib/auth.ts Review specific files
/mz:review --last 3 Review last 3 commits
/mz:verify Verify current phase deliverables
/mz:verify 5 Verify a specific phase
/mz:verify --partial Verify even with incomplete plans
/mz:verify --milestone v1.0 Audit all phases for milestone v1.0
/mz:map Analyze full codebase (4 areas)
/mz:map architecture Map architecture only
/mz:map tech Map tech stack only
/mz:plan add-phase "New feature" Add a phase to the roadmap
/mz:plan remove-phase 9 Remove an unstarted phase
/mz:plan insert-phase 6 "Hotfix" Insert phase after phase 6
/mz:discuss {topic} Brainstorm approaches for a topic
/mz:discuss 7 Brainstorm for phase 7 context
/mz:debug {issue} Debug an issue systematically
/mz:debug "tests failing in auth module" Debug with description
/mz:lifecycle Complete current milestone lifecycle
/mz:lifecycle v1.0 Archive milestone v1.0 specifically
/mz:lifecycle --skip-audit Skip audit and proceed to archive
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 · 91 lines · 14 tokens per session scan A 5c2e2359e8c2
help is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 945 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
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
vertical-construction
Domain knowledge for the construction vertical (contractors, field crews) so architect and pm don't spec construction products naively. Covers the vocabulary (bid vs estimate, takeoff, retainage, change order, AIA G702/G703, lien waiver, draw schedule), the non-obvious money rules that incumbents like Procore price…
pm
Project manager for GitHub issues: brainstorm design approaches, create structured issues optimized for LLM agent teams, triage and recommend what to work on next, audit and clean up stale issues, or deep-validate a single issue against the codebase. Triggers: create issue, plan work, new task, project manager, write…