save-context

A tool for saving a compact summary of the current coding session to a named file. It records the work context and, when available, recent Git branch and commit information.

In plain words
What is it for?
Saving progress, decisions, and repository state to a file in the current project's .memory directory.
Why use it?
It gives you a consistent checkpoint that can be read later instead of reconstructing the session from memory.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/adeotek/claude-code/save-context
Any agent
npx skills add adeotek/claude-code --skill save-context
Clone the repo
git clone --depth 1 https://github.com/adeotek/claude-code

Made for: Claude Code, Codex.

Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 825 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00108 $0.00825
Opus 5 $0.00054 $0.00413
Sonnet 5 $0.00022 $0.00165
Haiku 4.5 $0.00011 $0.00082

Measured yesterday against content hash 72a3ba36a727, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

save-context 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 yesterday.

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.

plugins/context-checkpoint/skills/save-context/SKILL.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Save Context

Save a compact summary of the current session to .memory/<name>.md in the current working directory, using fixed sections for consistent, scannable output.

Steps

  1. Extract the filename from the user's prompt. Convert to kebab-case (e.g., "auth work" → auth-work, "JWT feature" → jwt-feature). The display name in the heading preserves the user's original phrasing.

  2. Check for an existing file. If .memory/<name>.md already exists, ask the user whether to overwrite it before proceeding. Do not overwrite silently.

  3. Gather git state by running these commands:

    git branch --show-current 2>/dev/null
    git log --oneline -3 2>/dev/null
    

    If either fails (not a git repo), omit the git line from the output entirely.

  4. Create the .memory/ directory in the current working directory if it doesn't exist:

    mkdir -p .memory
    
  5. Write .memory/<name>.md using the template below, populated from the current conversation.

  6. Confirm the saved file path to the user (e.g., "Saved to .memory/auth-work.md").

Template

# Context: <user's original name>
**Saved**: YYYY-MM-DD | **Directory**: <absolute cwd>
**Branch**: <branch> | **Recent commits**: <hash> <msg>, <hash> <msg>, <hash> <msg>

## Goal
<What was being worked on and why — one focused paragraph>

## Current State
<What's done, what's in progress, what's blocked — be specific about status>

## Key Files
- `<path/to/file>` — <what changed or why it matters>

## Decisions Made
- **<decision>**: <rationale — especially non-obvious choices>

## Next Steps
- [ ] <concrete action item>

## Notes
<Caveats, gotchas, blockers, or background that would be easy to forget>

Omit the git line entirely if not in a git repo. Omit any section that has nothing meaningful to say — never write "N/A" or leave a section empty.

Content Guidelines

Goal: One paragraph describing the task and motivation. Focus on why, not just what.

Read the full file on GitHub · 75 lines

Changes

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.

  1. yesterday First seen · 75 lines · 108 tokens per session scan A 72a3ba36a727

Subscribe to this mod's changes

save-context is a skill published in the GitHub repository adeotek/claude-code (2 stars, last pushed 4mo ago), licensed MIT. It adds 108 tokens to every session and 825 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens