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/pausenpx skills add Sh3rd3n/megazord --skill pausegit 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/pause)<a href="https://agentmods.dev/skills/sh3rd3n/megazord/pause"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/pause.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.00012 | $0.00712 |
| Opus 5 | $0.00006 | $0.00356 |
| Sonnet 5 | $0.00002 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
pause 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mz:pause
Save current session context including progress, decisions, and modified files for seamless handoff to a future Claude Code session.
Reference @skills/init/design-system.md for all visual output formatting.
Step 1: Display Banner
╔═══════════════════════════════════════════════╗
║ ⚡ MEGAZORD ► PAUSE ║
╚═══════════════════════════════════════════════╝
Step 2: Load Context
Read .planning/STATE.md for current position and session continuity.
If STATE.md does not exist or .planning/ directory is missing, display:
╔═══════════════════════════════════════════════╗
║ ✗ No Megazord project found ║
╠═══════════════════════════════════════════════╣
║ Run /mz:init to set up your project first. ║
╚═══════════════════════════════════════════════╝
Then exit.
Read the current position data to build the pause description. Extract:
- Current phase number and name
- Current plan number
- Current status
Step 3: Stash Modified Files
Build a description string: "Phase {N}, Plan {M}, {status}"
Run via Bash to stash any modified files:
node {plugin_path}/bin/megazord.mjs tools stash pause --description "Phase {N}, Plan {M}, {status}"
Where {plugin_path} is the absolute path to the Megazord plugin directory (the root of this repository where package.json lives).
Parse the JSON result which contains:
success: booleanstashRef: string or null (the git stash reference if files were stashed)message: human-readable message
If success is false, display a warning but continue with the pause (stash failure should not block state updates).
Step 4: Update STATE.md
Run via Bash to update session continuity:
node {plugin_path}/bin/megazord.mjs tools state update-session --stopped-at "Phase {N}, Plan {M}, {status}" --stash-ref "{ref_or_None}" --last-error "None"
Also update the status to "Paused" via:
node {plugin_path}/bin/megazord.mjs tools state update-position --status "Paused"
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 · 97 lines · 12 tokens per session scan A 984ad4bada78
pause is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 712 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
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…
docs-refresh
Full documentation hygiene pass: memory, CLAUDE.md, lessons, references, guides. Audit freshness, delete stale, update outdated, compress index.
scratchpad
Persistent iteration memory — prevents Groundhog Day loops by recording what was tried, what failed, and what to try next.
lembas
Use between workflow phases or when context feels bloated. Compresses the current conversation into a structured summary capturing task, findings, files, state, and next steps. Invoke standalone or automatically between quest phases.
brain-uninstall
Use when users want to remove or disconnect the mybrain plugin's persistent memory layer. Handles teardown for all database strategies (Docker, local PostgreSQL, remote PostgreSQL), config file removal, and offers a disconnect-only option that preserves the database.
brain-hydrate
Use when users want to bootstrap the brain with existing project knowledge -- reading ADRs, feature specs, UX docs, commit history, and error patterns to seed institutional memory on a project that already has artifacts on disk. Also use for incremental re-hydration after significant work outside the pipeline.…