session-summary

session-summary is a skill for Claude Code from jerpint/woltspace. It costs 25 tokens per session (816 once invoked), scanned A, original, MIT.

A session-recording skill that writes a short summary of what happened, what was made, and any resulting link or decision. It stores the summary on disk for later sessions or a Telegram bot to read.

In plain words
What is it for?
Use it after meaningful work to record the outcome, related artifact, reason, and tags.
Why use it?
It prevents useful work and decisions from being lost when a session ends.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the woltspace plugin — 14 skills shipped together

Good fit Use it after meaningful work to record the outcome, related artifact, reason, and tags.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jerpint/woltspace/session-summary
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 jerpint/woltspace --skill session-summary
Clone the repo
git clone --depth 1 https://github.com/jerpint/woltspace

Made for: Claude Code.

Or install woltspace, the plugin that ships this one along with the rest of its 14 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-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/jerpint/woltspace/session-summary/github.svg)](https://agentmods.dev/skills/jerpint/woltspace/session-summary)
Your own site
<a href="https://agentmods.dev/skills/jerpint/woltspace/session-summary"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/session-summary/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.

agentmods 80×15 button for session-summary

Your own site · 80×15
<a href="https://agentmods.dev/skills/jerpint/woltspace/session-summary"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/session-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 816 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.
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.00025 $0.00816
Opus 5 $0.00013 $0.00408
Sonnet 5 $0.00005 $0.00163
Haiku 4.5 $0.00003 $0.00082

Measured 6d ago against content hash 2224b2118c0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-15, from the pricing page.

Security

Grade A, and why

session-summary 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 6d 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.

container/skills/session-summary/SKILL.md · 95 lines

How it starts

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

Session Summary Skill

Write a short summary of what happened this session so the bot has context between sessions.

When to use

Run at the end of a session — or anytime something meaningful was made (artifact, decision, significant change).

What to write

Reflect honestly on the session. Answer:

  • What was the main thing that happened or got built?
  • Did anything come out of it (link, file, decision)?
  • Why did it matter or what drove it?

Keep it fluid — 1-3 sentences max. No bullet lists. Write like you'd tell someone what you did.

Format

{
  "id": "sess_<timestamp>",
  "t": <unix seconds>,
  "title": "<3-6 word label>",
  "artifact": { "type": "<type>", "url": "<url>", "label": "<label>" },
  "summary": "<1-3 sentence prose>",
  "tags": ["tag1", "tag2"]
}
  • artifact is optional — omit entirely if nothing linkable came out
  • artifact.type: spotify_playlist, digest, html_page, code, config, decision
  • tags: 2-5 lowercase words (e.g. music, bot, infra, memory, site)

How to write it

Run this node one-liner, filling in the fields:

node -e "
const {appendFileSync, mkdirSync} = require('fs');
const woltDir = process.env.WOLTSPACE_WOLT_DIR || '/workspace/wolt';
const stateDir = woltDir + '/.state';
mkdirSync(stateDir, {recursive: true});
const entry = {
  id: 'sess_' + Date.now().toString(36),
  t: Math.floor(Date.now() / 1000),
  title: 'YOUR TITLE HERE',
  artifact: { type: 'TYPE', url: 'URL', label: 'LABEL' },
  summary: 'YOUR SUMMARY HERE.',
  tags: ['tag1', 'tag2']
};
appendFileSync(stateDir + '/sessions.jsonl', JSON.stringify(entry) + '\n');
console.log('session summary written:', entry.id);
"

Drop the artifact key if there's nothing to link.

Example

node -e "
const {appendFileSync, mkdirSync} = require('fs');
const woltDir = process.env.WOLTSPACE_WOLT_DIR || '/workspace/wolt';
const stateDir = woltDir + '/.state';
mkdirSync(stateDir, {recursive: true});
const entry = {
  id: 'sess_' + Date.now().toString(36),
  t: Math.floor(Date.now() / 1000),
  title: 'morning building playlist',
  artifact: {
    type: 'spotify_playlist',
    url: 'https://open.spotify.com/playlist/abc123',
    label: \"Arthur's Morning Build\"
  },
  summary: 'made a 12-track playlist for focused building — ólafur arnalds, nils frahm, boards of canada. anchored around texture not rhythm, nothing with words. jerpint mentioned he builds best with ambient instrumental.',
  tags: ['music', 'playlist', 'morning', 'focus']
};
appendFileSync(stateDir + '/sessions.jsonl', JSON.stringify(entry) + '\n');
console.log('written:', entry.id);
"

Read the full file on GitHub · 95 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. 6d ago First seen · 95 lines · 25 tokens per session scan A 2224b2118c0b

Subscribe to this mod's changes

session-summary is a skill published in the GitHub repository jerpint/woltspace (12 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 816 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-09.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

shellm

Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.

laude-institute/headlong · 49 tokens