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 verifygit 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/verify)<a href="https://agentmods.dev/skills/sh3rd3n/megazord/verify"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/verify/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/skills/sh3rd3n/megazord/verify"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/verify.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.00009 | $0.02953 |
| Opus 5.5 | $0.00004 | $0.01181 |
| Sonnet 5.5 | $0.00002 | $0.00591 |
| Haiku 4.5 | $0.00001 | $0.00295 |
Grade A, and why
verify 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 1mo 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mz:verify
Verify that a phase achieved its GOAL by performing goal-backward verification against ROADMAP.md success criteria and PLAN.md must_haves. Spawns a verifier subagent via the Task tool that checks truths, artifacts (3-level), key links, and requirement coverage against the actual codebase. Produces VERIFICATION.md with results.
Note: This skill always works when invoked manually, regardless of the workflow.verifier config setting. The config toggle only controls whether /mz:go automatically suggests verification after execution.
Reference @skills/init/design-system.md for visual output formatting.
Reference @skills/shared/presentation-standards.md for content formatting rules.
Reference @skills/shared/terminology.md for official term definitions.
Reference @skills/verify/verifier.md for verification protocol and spawning patterns.
Step 1: Display Banner
Output the stage banner:
+===============================================+
| MEGAZORD > VERIFY |
+===============================================+
Step 2: Load Context and Validate
Read .planning/megazord.config.json. If missing, display error and stop:
## Error
Project not initialized — no megazord.config.json found.
`/mz:init`
If config exists, continue loading:
- Read
.planning/STATE.mdfor current position. - Read
.planning/ROADMAP.mdfor phase details and success criteria.
Parse the user's message (text after /mz:verify) for arguments:
{phase_num}-- verify a specific phase (optional, defaults to current)--partial-- verify even if some plans are incomplete (skip completion check)--milestone {version}-- run milestone audit mode instead of phase verification (see Step 3b)
Determine the plugin path for CLI commands:
- Read
plugin_pathfrom the config JSON. - If
plugin_pathis not set in config, try~/.claude/plugins/mz. Check if~/.claude/plugins/mz/bin/megazord.mjsexists. - If neither exists, display error and stop:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 387 lines · 9 tokens per session scan A 4033ea26024b
verify is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 2,953 once invoked, about $0.0000 per session on Opus 5.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
status
Maintain the repository's STATUS.md — the fixed-shape status file an external chief-of-staff agent reads to brief the founder. Applies to every session; update it in the same commit as the work and before the final message.
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs.
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.