session-done

session-done is a skill for Codex from vincentkoc/dotskills. It costs 36 tokens per session (706 once invoked), scanned A, original, MIT.

A procedure for creating a concise session handoff when a user asks to wrap up or use /done. It can return the handoff in chat or write a requested Markdown file to one named destination.

In plain words
What is it for?
Use it to prepare continuation notes for another developer or a later session, optionally saving them in a requested documentation or notes folder.
Why use it?
It captures completed work, validation limits, blockers, and next actions without deleting work, releasing ownership, or copying sensitive session data.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to prepare continuation notes for another developer or a later session, optionally saving them in a requested documentation or notes folder.

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

Made for: Codex.

Its marketplace also offers this one on its own, as the plugin session-done — /plugin install session-done after adding the marketplace above.

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-done

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/vincentkoc/dotskills/session-done"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/session-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 706 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.00036 $0.00706
Opus 5.5 $0.00014 $0.00282
Sonnet 5.5 $0.00007 $0.00141
Haiku 4.5 $0.00004 $0.00071

Measured 1mo ago against content hash 97a743085856, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

session-done 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 1mo 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.

skills/session-done/SKILL.md · 55 lines

How it starts

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

Session Done

Purpose

Capture the outcome, evidence, unresolved work, and next action without making session completion a cleanup or memory-write command.

When to use

  • The user asks for a session handoff, continuation summary, or /done.
  • The user requests a durable Markdown handoff, including a note in a PKM/Obsidian folder.

Workflow

  1. Use the current task's evidence. Record completed work, validation and its limits, blockers, and the next owner/action. Do not scan unrelated sessions or copy credentials, private logs, or raw transcripts.
  2. Include known session, branch, commit/PR, and retained-checkout identities when relevant. Mark unknown facts as unknown. Completion does not terminate sessions, remove worktrees, release owners, or rerun cleanup.
  3. Return the handoff in chat by default. For deterministic Markdown, run python3 scripts/session-done --summary "..." --state "..." --follow-ups "..."; it writes only stdout.
  4. If the user explicitly requested retention, use one named destination with --output <new-path>. The parent must already exist; existing files and symlinks are refused. A PKM/Obsidian folder can be that destination, without a second copy or sync service.
  5. Report the created path or exact failure. A failed write is not saved evidence. Preserve existing notes and recovery material; do not retry under new filenames automatically.
  6. Update memory only when the user directly requests it, through the environment's existing memory workflow. This writer never appends to shared memory or edits agent-managed memory files. Report that separate action's outcome.

Inputs

  • At least one content flag: --summary, --decisions, --questions, --follow-ups, --state, --reflection, or --flashcards.
  • Optional --session-id and --branch: verified values; both default to unknown.
  • Optional --output: the explicitly requested new Markdown file. No environment variable enables retention, copying, or memory writes.

Outputs

Read the full file on GitHub · 55 lines

Files

What ships with it

3 files 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. 1mo ago First seen · 55 lines · 36 tokens per session scan A 97a743085856

Subscribe to this mod's changes

session-done is a skill published in the GitHub repository vincentkoc/dotskills (109 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 706 once invoked, about $0.0001 per session on Opus 5.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-15.