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/nguyenthienthanh/aura-frog/session-continuationnpx skills add nguyenthienthanh/aura-frog --skill session-continuationgit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/nguyenthienthanh/aura-frog/session-continuation)<a href="https://agentmods.dev/skills/nguyenthienthanh/aura-frog/session-continuation"><img src="https://agentmods.dev/badge/skills/nguyenthienthanh/aura-frog/session-continuation.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.00022 | $0.00428 |
| Opus 5 | $0.00011 | $0.00214 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
session-continuation 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 2d 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
AI-consumed reference. Optimized for Claude to read during execution. Human-readable explanation: see docs/architecture/HIERARCHICAL_PLANNING.md or docs/getting-started/ depending on topic.
Session Continuation
Manage workflow state across sessions.
Triggers
Token ≥75% → suggest handoff. User says handoff/save → execute. User says resume + ID → load.
Handoff Flow
- Save to
.claude/logs/runs/[id]/run-state.json: workflow_id, status, current_phase, agents, phases_completed (with deliverables), key decisions, token_usage - Output: workflow ID, phase progress, deliverables, resume command
Resume Flow
- Load state file → validate exists/valid
- Restore: project context, agents, phase rules, decisions
- Show summary → continue from saved phase
Auto-Save
Phase completion, every 5 min, token milestones (100K/150K/175K). Silent except warning thresholds.
TOON State Format (~160 tokens vs JSON ~600)
workflow:
id: AUTH-1234
phase: 3
status: in_progress
agents[2]: architect,tester
Error Handling
Not found → show available, suggest /run. Corrupted → restore from .backup.json.
Cleanup
Completed: 30 days. Cancelled: 7 days. Paused: indefinitely.
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.
- 2d ago First seen · 62 lines · 22 tokens per session scan A e44ec5367bf6
session-continuation is a skill published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 428 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-09-03.
Other skills, from other repositories
gsd-capture
Capture ideas, tasks, notes, and seeds to their destination.
gsd-ns-ideate
Route to the appropriate exploration / capture skill based on the user's intent. gsd-note, gsd-add-todo, gsd-add-backlog, and gsd-plant-seed were folded into gsd-capture (with --note, default, --backlog, --seed modes) by #2790. The capture target lists pending todos via --list.
recipe-diagnose
Investigate problem, verify findings, and derive solutions.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-reverse-engineer
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow.
recipe-design
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval.