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 gogit 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/go)<a href="https://agentmods.dev/skills/sh3rd3n/megazord/go"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/go.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.1 | $0.00015 | $0.05911 |
| Opus 5 | $0.00008 | $0.02955 |
| Sonnet 5 | $0.00003 | $0.01182 |
| Haiku 4.5 | $0.00002 | $0.00591 |
Grade A, and why
go 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 7d 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 — 674 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mz:go
Execute the current phase plan by orchestrating executor agents. Supports two execution modes: subagent delegation (Task tool, fire-and-forget) and Agent Teams (TeamCreate, SendMessage, shared TaskList with real-time coordination). Auto-detects the optimal mode per wave based on plan complexity, with --teams/--no-teams overrides.
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/go/executor.md for execution protocol and spawning patterns.
Reference @skills/go/teams.md for Agent Teams execution protocol.
Step 1: Display Banner
Output the stage banner:
+===============================================+
| MEGAZORD > EXECUTE |
+===============================================+
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.
Determine review configuration from the config:
- If
config.quality.review === "auto":review_enabled = true,review_mode = "auto" - If
config.quality.review === "manual":review_enabled = true,review_mode = "manual" - If
config.quality.review === "off":review_enabled = false
If review is disabled, display a one-time notice:
> Note: Code review is disabled (quality.review: "off"). Tasks will not be reviewed.
Determine TDD configuration:
- If
config.quality.tdd === true:tdd_enabled = true - Otherwise:
tdd_enabled = false
Determine CORTEX configuration:
- If
config.quality.cortex === true:cortex_enabled = true - Otherwise:
cortex_enabled = false
Display activation notices (same pattern as the review disabled notice):
- If TDD is enabled:
> TDD mode active: RED-GREEN-REFACTOR enforced per task - If CORTEX is enabled:
> CORTEX classification active: tasks classified before execution
What ships with it
2 files 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.
- 7d ago First seen · 674 lines · 15 tokens per session scan A 2a1dc3af84a4
go is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 5,911 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
finding-duplicate-functions
Use when auditing a codebase for semantic duplication — functions that do the same thing but have different names or implementations, especially common in LLM-generated codebases.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
sync-check
Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs"…
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.