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 resumegit 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/resume)<a href="https://agentmods.dev/skills/sh3rd3n/megazord/resume"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/resume/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/resume"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/resume.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.00011 | $0.01151 |
| Opus 5 | $0.00005 | $0.00575 |
| Sonnet 5 | $0.00002 | $0.00230 |
| Haiku 4.5 | $0.00001 | $0.00115 |
Grade A, and why
resume 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 9d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mz:resume
Restore context from a previous session and display current project state. Shows what was being worked on, restores any stashed files, and suggests the next action -- but does NOT auto-execute.
Reference @skills/init/design-system.md for all visual output formatting.
Step 1: Display Banner
╔═══════════════════════════════════════════════╗
║ ⚡ MEGAZORD ► RESUME ║
╚═══════════════════════════════════════════════╝
Step 2: Load Context
Read .planning/STATE.md for session continuity and current position.
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.
Extract from STATE.md:
- Session continuity: last session date, stopped at, resume file, stash ref, last error
- Current position: phase, plan, status, progress
Step 3: Restore Stash (if applicable)
Read the stash ref from session continuity.
If stash ref exists and is not "None":
Run via Bash to restore stashed files:
node {plugin_path}/bin/megazord.mjs tools stash resume --stash-ref "{stash_ref}"
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:
- If
successis true: files were restored. Clear the stash ref in STATE.md by running:node {plugin_path}/bin/megazord.mjs tools state update-session --stash-ref "None" - If
successis false and message contains "not found": display note "No pause checkpoint found -- showing last known position" (best-effort recovery) - If
successis false and message contains "CONFLICT": display warning with resolution steps:⚠ Stash conflicts detected. To resolve: 1. Run `git stash show` to see conflicting files 2. Resolve conflicts manually 3. Run `git stash drop` to clean up
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.
- 9d ago First seen · 146 lines · 11 tokens per session scan A 8eca8fe22c7d
resume is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 1,151 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
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…
alive:my-context-graph
Render an interactive map of your world. Generates the world index from all walnut and bundle frontmatter, then produces a force-directed graph showing connections between walnuts, people, bundles, and tags. Opens in the browser.