session-memory

session-memory is a skill for Claude Code from oaustegard/claude-skills. It costs 94 tokens per session (1,415 once invoked), scanned A, original, MIT.

A running-notes system for preserving important decisions, corrections, files, and errors during a long work session. It keeps continuity when the conversation becomes large or is compressed.

In plain words
What is it for?
Use it to start, update, or review structured notes about the current task and its progress.
Why use it?
It reduces the risk of losing useful session context before the work is finished.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the knowledge-and-memory plugin — 3 skills shipped together

Good fit Use it to start, update, or review structured notes about the current task and its progress.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oaustegard/claude-skills/session-memory
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.

Any agent
npx skills add oaustegard/claude-skills --skill session-memory
Clone the repo
git clone --depth 1 https://github.com/oaustegard/claude-skills

Made for: Claude Code.

Or install knowledge-and-memory, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

agentmods badge for session-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/oaustegard/claude-skills/session-memory.svg)](https://agentmods.dev/skills/oaustegard/claude-skills/session-memory)
Your own site
<a href="https://agentmods.dev/skills/oaustegard/claude-skills/session-memory"><img src="https://agentmods.dev/badge/skills/oaustegard/claude-skills/session-memory.svg" alt="Measured on agentmods" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00094 $0.01415
Opus 5 $0.00047 $0.00707
Sonnet 5 $0.00019 $0.00283
Haiku 4.5 $0.00009 $0.00142

Measured 5d ago against content hash 39887989eb68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

session-memory 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.

plugins/knowledge-and-memory/skills/session-memory/SKILL.md · 154 lines

How it starts

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

Session Memory - Running Notes

Maintain a single structured markdown document that tracks what is happening right now in the current work session. This is within-session continuity, distinct from remember() (cross-session semantic memory) and stash (coarse checkpoint).

When to Use

Invoke on any of these triggers:

  • User says "session notes", "update notes", "start session notes", "show session notes", "note the session", "write it down"
  • User indicates they want continuity across context compression: "before you forget", "write that down", "for when context gets compressed"
  • You have independently completed a meaningful block of work (file edits, a bugfix, a design choice, a reversal after correction) and no note has been updated for a while

Do NOT invoke for:

  • One-off answers with no follow-up
  • Cross-session persistence — that's remember()
  • Coarse checkpoints intended for another session to resume — that's stash

Template (Fixed Sections)

Every session note uses exactly these sections, in this order, with these headers. Preserve the structure on every update. Never rename or reorder sections. Update the content within sections; leave empty sections present with a single _(nothing yet)_ placeholder.

# Session: {short title, 3-8 words, derived from the initial task}

## Current State
_What is actively being worked on right now. Explicit next step._

## Task Specification
_What the user originally asked for. Constraints, acceptance criteria,
design decisions that framed the work._

## Files and Functions
_Important paths touched or referenced, one per line, with a one-line
note on what they contain and why they matter._

## Errors & Corrections
_Errors encountered and how they were fixed. User corrections to my
approach — these have priority over routine progress entries._

## Key Decisions
_Choices made during the session with their rationale. One bullet per
decision. Lead with the choice, then the why._

## Worklog
_Terse, append-only, chronological. One line per attempt or step.
Prefix with ✓ (done), ✗ (failed), → (in progress), or ↺ (reverted)._

Read the full file on GitHub · 154 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 5d ago First seen · 154 lines · 94 tokens per session scan A 39887989eb68

Subscribe to this mod's changes

session-memory is a skill published in the GitHub repository oaustegard/claude-skills (147 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 1,415 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-09-03.

Related

Other skills, from other repositories

relay

Capture the full context of the CURRENT Claude chat into a complete, portable briefing the user can paste into a NEW chat to continue seamlessly. Use ONLY when the user explicitly asks — e.g. "relay", "relay this", "handover", "hand off", "handoff", "continue in a new chat", "this chat is getting long", "carry this…

mosuvo/relay · 164 tokens

context-summary

Produces a lean, paste-ready session handoff so work can continue in a new conversation without re-paying the cost of the full chat. Emits a seven-block skeleton optimized for re-entry, not archival. Trigger this skill whenever the user says any of the following (exact or close paraphrase): "context summary"…

thebpandey/context-summary · 180 tokens

company-brain

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…

coreyhaines31/makerskills · 322 tokens

claude-md-updater

Scans the session for lessons and workflows, then proposes scoped CLAUDE.md edits. Use for save this lesson or add to context.

jamditis/claude-skills-journalism · 34 tokens

superdesign

Design or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models. Use whenever the user wants to design a page, feature, flow, slide deck, or brand-new product; improve or reproduce existing UI; compare design results across top models; explore visual variants…

superdesigndev/superdesign-skill · 115 tokens

continuous-learning-construction

Automatically extract patterns, best practices, and reusable knowledge from construction automation sessions to improve future performance.

datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction · 24 tokens