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.
git clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/commands/eddiebelaval/squire/resume)<a href="https://agentmods.dev/commands/eddiebelaval/squire/resume"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/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/commands/eddiebelaval/squire/resume"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/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.00006 | $0.00403 |
| Opus 5 | $0.00003 | $0.00201 |
| Sonnet 5 | $0.00001 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
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 5d 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.
What it actually says
/resume - Resume Development Session
You are helping resume work from a previous session that may have crashed or timed out.
Recovery Process
Step 1: Check for Recoverable Sessions
Run the recovery check to see what sessions need attention:
cd ~/Development/session-resilience-agents && npm run resume
Step 2: Review Session State
If a session is found, you'll see:
- Session ID and project name
- Current progress percentage
- Last active timestamp
- Current phase and task
- Files that were modified
- Decisions that were made
Step 3: Context Restoration
After resuming, restore the development context:
- Read the session's recovery instructions
- Check the plan file at
~/.claude/plans/for full task list - Review git history for recent commits
- Read any files that were in progress
Step 4: Continue Development
With context restored:
- Mark current task as in_progress if not already
- Continue from where work stopped
- Session state auto-saves every 5 tool uses
- Use
/save-statefor immediate checkpoint
Integration with Agents
The session state includes agent assignments for each task. When resuming:
- Check
assignedAgentfor the current task - Delegate to that agent if appropriate
- MCP tools are listed in
assignedMcp
Examples
Resume the most recent session:
/resume
Resume a specific session:
/resume abc123-def456
Quick Reference
| Command | Purpose |
|---|---|
npm run resume |
Interactive resume |
npm run status |
Check current state |
npm run checkpoint |
Force save |
npm run list |
See all sessions |
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.
- 5d ago First seen · 74 lines · 6 tokens per session scan A 472c5c38cef7
resume is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It adds 6 tokens to every session and 403 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-09-03.
Other commands, from other repositories
paul:handoff
Generate comprehensive session handoff document.
paul:progress
Smart status with routing - suggests ONE next action.
paul:pause
Create handoff file and prepare for session break.
context-health
Dashboard de salud del contexto activo con predicción de degradación y recomendaciones de compactación. Usa cuando el usuario dice "context health", "salud del contexto", "degradation", "compactar contexto", "context overflow", "tokens", "session health", "compact", "contexto lleno". Monitorea degrdación del contexto…
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
capturar
Capturar ideas y notas sin interrumpir el flujo de trabajo. Usa cuando el usuario dice "capturar idea", "quick note", "nota rápida", "grab this", "take a note", "guardar idea", "note to self", "capture thought", "I should remember", "guardar esto". Guarda en memoria persistente sin romper el contexto actual.