woltspace-session-summary

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

A short record of a coding session saved to disk so a Telegram bot can answer what was built or decided.

In plain words
What is it for?
Summarize a completed build, meaningful change, decision, or other session result in a small structured JSON record.
Why use it?
It preserves the session’s useful outcome, such as a file, link, decision, or artifact, when the conversation itself is no longer available.

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/jerpint/woltspace/woltspace-session-summary
Any agent
npx skills add jerpint/woltspace --skill woltspace-session-summary
Clone the repo
git clone --depth 1 https://github.com/jerpint/woltspace

Made for: Claude Code, Codex.

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 woltspace-session-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/jerpint/woltspace/woltspace-session-summary.svg)](https://agentmods.dev/skills/jerpint/woltspace/woltspace-session-summary)
Your own site
<a href="https://agentmods.dev/skills/jerpint/woltspace/woltspace-session-summary"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/woltspace-session-summary.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 813 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.00028 $0.00813
Opus 5 $0.00014 $0.00407
Sonnet 5 $0.00006 $0.00163
Haiku 4.5 $0.00003 $0.00081

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

Security

Grade A, and why

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

container/skills/woltspace-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.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.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. 5d ago First seen · 95 lines · 28 tokens per session scan A 7c17154acdc7

Subscribe to this mod's changes

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

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

agent-memory

../../../engineering/agent-memory/skills/agent-memory/SKILL.md.

alirezarezvani/claude-skills · 0 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