verify

verify is a skill for Claude Code from Sh3rd3n/megazord. It costs 9 tokens per session (2,953 once invoked), scanned A, original, MIT.

A project-checking workflow that compares completed work with its stated acceptance criteria. Acceptance criteria are the conditions a result must meet to count as complete.

In plain words
What is it for?
Use it to review a project phase against its roadmap and plan, inspect the codebase, and produce a VERIFICATION.md report.
Why use it?
It helps uncover missing requirements, weak evidence, broken links, or deliverables that do not achieve the project goal.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions subagents.

Part of the mz plugin — 16 skills, 16 commands, 6 agents, 2 hooks shipped together

Good fit Use it to review a project phase against its roadmap and plan, inspect the codebase, and produce a VERIFICATION.md report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sh3rd3n/megazord/verify
Install

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.

Any agent
npx skills add Sh3rd3n/megazord --skill verify
Clone the repo
git clone --depth 1 https://github.com/Sh3rd3n/megazord

Made for: Claude Code.

Or install mz, the plugin that ships this one along with the rest of its 16 skills, 16 commands, 6 agents, 2 hooks.

Wrote 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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/sh3rd3n/megazord/verify/github.svg)](https://agentmods.dev/skills/sh3rd3n/megazord/verify)
Your own site
<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.

agentmods 80×15 button for verify

Your own site · 80×15
<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>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,953 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 4033ea26024b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/verify/SKILL.md · 387 lines

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.md for current position.
  • Read .planning/ROADMAP.md for 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:

  1. Read plugin_path from the config JSON.
  2. If plugin_path is not set in config, try ~/.claude/plugins/mz. Check if ~/.claude/plugins/mz/bin/megazord.mjs exists.
  3. If neither exists, display error and stop:

Read the full file on GitHub · 387 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 387 lines · 9 tokens per session scan A 4033ea26024b

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories