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/quicknpx skills add Sh3rd3n/megazord --skill quickgit 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/quick)<a href="https://agentmods.dev/skills/sh3rd3n/megazord/quick"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/quick.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.00009 | $0.01279 |
| Opus 5 | $0.00005 | $0.00639 |
| Sonnet 5 | $0.00002 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
quick 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mz:quick
Execute a one-off task with atomic commit tracking. Skips roadmap and phase planning but respects quality gates from project config. Works with or without an active Megazord project.
Reference @skills/init/design-system.md for all visual output formatting.
Reference @skills/shared/terminology.md for official term definitions.
Step 1: Display Banner
╔═══════════════════════════════════════════════╗
║ ⚡ MEGAZORD ► QUICK ║
╚═══════════════════════════════════════════════╝
Step 2: Load Config
Read .planning/megazord.config.json.
If config exists: Parse it and note quality settings (TDD, review mode). These will be applied during execution.
If config does not exist: That is OK -- quick tasks work without a project. Use defaults:
- TDD: off
- Review: off
- Commit docs: true
Step 3: Parse Task Description
Look for the task description in the user's message after /mz:quick.
If a description is provided (e.g., /mz:quick fix the typo in README.md):
- Use the text after
/mz:quickas the task description.
If no description is provided (just /mz:quick with nothing after):
- Use AskUserQuestion:
- header: "Quick" (5 chars)
- question: "What do you want to do?"
- (freeform text response)
Step 4: Create Quick Task Directory
Generate a sequential task number and slug:
- Check
.planning/quick/directory for existing task directories. - Find the highest existing number (from directory names like
001-fix-typo/), add 1. If none exist, start at 001. - Generate a slug from the description: lowercase, replace spaces/special chars with hyphens, max 30 characters.
- Create the directory:
.planning/quick/{NNN}-{slug}/
Write a minimal plan file at .planning/quick/{NNN}-{slug}/{NNN}-PLAN.md:
---
type: quick
task: {NNN}
description: "{task description}"
created: {ISO date}
---
<objective>
{task description}
</objective>
<tasks>
<task type="auto">
<name>Task 1: {task description}</name>
<action>{task description}</action>
<done>{task description} completed and committed.</done>
</task>
</tasks>
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 · 184 lines · 9 tokens per session scan A 08dc4e377b80
quick is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,279 once invoked, about $0.0000 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…
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…
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.
performance-audit
Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…
add
Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer…
logic-diff
Compare two code versions for semantic equivalence via semi-formal tracing of both versions side-by-side. Trigger when the user shares a refactor, rewrite, migration, or A/B implementation and wants to confirm behavior is unchanged — "did I break anything", "is this equivalent", "are these equivalent", "semantically…