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/ilyagorsky/memory-toolkit/session-continuenpx skills add IlyaGorsky/memory-toolkit --skill session-continuegit clone --depth 1 https://github.com/IlyaGorsky/memory-toolkitWhat 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.00024 | $0.00557 |
| Opus 5 | $0.00012 | $0.00279 |
| Sonnet 5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
session-continue 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
/session-continue — Quick Continue
Pick up a workstream without a full cold start. For cases when you know what you're doing.
Step 1: Find handoff
MEM="${CLAUDE_PLUGIN_ROOT}/scripts/memory.js"
PROJ_KEY=$(pwd | tr '/.' '-' | sed 's/^-//')
MEM_DIR="$HOME/.claude/projects/-${PROJ_KEY}/memory"
node "$MEM" --dir="$MEM_DIR" handoff "${1:-}"
Falls back to global handoff if no per-workstream file exists. Prints NO_HANDOFF when neither found.
If no handoff exists → suggest /session-start instead.
Step 2: Git status (silently)
git status --short
git log --oneline -3
git branch --show-current
If there are uncommitted changes — show in one line. If the tree is clean — don't mention it.
Step 3: Show summary
Format (10 lines max):
## Continuing: {workstream}
**Where we left off:** {from handoff — last action}
**What's next:** {from handoff — next step}
**Branch:** {branch} {uncommitted count if any}
Shall we begin?
Don't show task plan, focus candidates, model recommendations — that's for /session-start.
Step 4: Load context on demand
MUST wait for explicit user confirmation ("yes", "go", a number, or similar) before proceeding. Do NOT auto-continue after showing the summary.
If the user confirmed — load only what's needed for the next step:
- The file that was last edited
- Task plan if available
- Last 3 feedback entries via
node $MEM search
Do NOT load the entire memory — only what's relevant.
Step 5: Mark
node $MEM_DIR/memory.js note "SESSION_CONTINUE branch:$(git branch --show-current) workstream:{name}"
Rules
- Maximum speed — 10 lines of output, then get to work
- Don't ask about the model, don't show candidates — the user already knows
- If handoff is older than 7 days — warn: "Handoff from {date}, context may be stale. /session-start for a full overview?"
- If no argument is passed — take the workstream from the latest handoff
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 · 88 lines · 24 tokens per session scan A b7b759ebd236
session-continue is a skill published in the GitHub repository IlyaGorsky/memory-toolkit (13 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 557 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-30.
Other skills, from other repositories
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
math-unicode
Use when a response needs mathematical notation (equations, filters, set-builder notation, statistics, calculus, linear algebra, logic, ratios, drops, counts) and the output goes to a terminal or TUI that cannot render LaTeX: Claude Code, Codex CLI, SSH and tmux sessions, CI logs. Load it before composing, including…
vibe-ship
Generates a complete, production-ready deployment setup for any app in one pass -- Dockerfile, docker-compose.yml, .dockerignore, CI/CD (GitHub Actions), scalability config (health checks, resource limits, K8s on request), and security hardening (non-root user, secrets, dependency scanning). Auto-detects the stack…
anatomia-cc
ES: Te dice qué construir en Claude Code y te da el esqueleto de archivos: skill y en qué modo, subagente, hook, servidor MCP, plugin, rutina, artefacto, app con el Agent SDK, una línea en CLAUDE.md, o nada. Corré esto antes del primer archivo. Se dispara con «esto lo hago como skill o como agente», «necesito un MCP o…
create-agents-md
Create concise, repository-specific AGENTS.md files with operational contract, precedence rules, and drift-control guidance.
create-checkpoint
Capture the current session state as a checkpoint artifact per spec section 4.4. Use when the user signals session end or explicitly requests a checkpoint. Do not use mid-session or without user approval.