session-close

A guide for closing a coding-agent session with saved repository state, suitable checks, updated documentation, and a handoff for later work. It covers reviewing changes, required tests, generated files, and commits or pushes.

In plain words
What is it for?
Use it when wrapping up a session, preparing a final commit and push, reconciling documentation, or writing a useful report of remaining work.
Why use it?
It reduces the chance of losing track of unfinished changes, skipped verification, outdated documentation, or work that was never handed over clearly.

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/takeoff69/codex-skills-kit/session-close
Any agent
npx skills add TAKEOFF69/codex-skills-kit --skill session-close
Clone the repo
git clone --depth 1 https://github.com/TAKEOFF69/codex-skills-kit

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 931 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.00059 $0.00931
Opus 5 $0.00030 $0.00465
Sonnet 5 $0.00012 $0.00186
Haiku 4.5 $0.00006 $0.00093

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

Security

Grade A, and why

session-close 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 3d 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-close/SKILL.md · 137 lines

How it starts

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

Session Close

Turn active session into recoverable, reviewable handoff without absorbing unrelated work.

This is lightweight closeout. Use retro-distill for deeper pattern mining after major chunks or failures.

Authority order

  1. Read repository AGENTS.md and nested instructions governing changed paths.
  2. Use repository-native closeout, worktree, documentation, and verification commands when defined.
  3. Apply generic workflow below only where repository has no stronger rule.

Workflow

1. Inventory live state

Capture:

git rev-parse --show-toplevel
git branch --show-current
git rev-parse HEAD
git status --porcelain
git diff --name-only
git diff --cached --name-only
git log --oneline -10

Identify owned paths, unrelated dirty paths, commits made this session, and unpushed commits. Do not clean or stage yet.

2. Map changes to obligations

For each owned change, identify:

  • tests or probes required by affected surface
  • documentation that describes changed behavior
  • generated artifacts needing repository-native regeneration
  • release or deployment boundary
  • session log or handoff format required by repository

Use live paths and current code. Prior plans record intent, not necessarily final state.

3. Reconcile documentation

Update canonical docs when behavior, architecture, commands, data contracts, or operator workflows changed. Avoid documentation churn for implementation details with no durable effect.

If required doc cannot be updated, record explicit exception with reason and follow-up owner. Do not silently leave known drift.

4. Verify proportionally

Use verify-honestly:

  • run cheapest probe capable of catching likely failure
  • cite existing green deterministic gates instead of repeating them
  • verify UI in browser when UI behavior changed
  • name live or production gaps instead of implying coverage
  • record exact commands and results

5. Write handoff

Use repository session-log format when present. Otherwise record concise Markdown with:

Read the full file on GitHub · 137 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. 3d ago First seen · 137 lines · 59 tokens per session scan A be93dd059792

Subscribe to this mod's changes

session-close is a skill published in the GitHub repository TAKEOFF69/codex-skills-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 931 once invoked, about $0.0003 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

manage-codex-skills

Inventory, classify, route, catalog, relocate, or validate Codex skills and generate a skills menu. Use for skill-library organization or when Codex must find task-relevant skills. Classification, relocation, creation, revision, and promotion require user approval.

WildPigKing/codex-project-skill-manager · 58 tokens

reflect-codex-workflows

Compare evidence from a current or completed project with installed skills and decide whether to reuse, revise, create, or not skill the lesson. Use for workflow reflection or proposed skill upgrades. Do not edit skills without explicit authorization.

WildPigKing/codex-project-skill-manager · 51 tokens

bootstrap-codex-workspace

Inspect a Windows or macOS Codex environment and produce a read-only, approval-bound plan for the global AGENTS.md path, user skills root, and root for future projects. Use for workspace setup, bootstrap, or location planning. Do not write outside the repository until the user approves the exact plan ID.

WildPigKing/codex-project-skill-manager · 69 tokens

maintain-project-ai-records

Initialize and maintain lightweight AI work records in a writable project. Use on the first substantive writable task and after meaningful milestones. Do not create records for read-only inspection or trivial answers.

WildPigKing/codex-project-skill-manager · 43 tokens

organize-codex-projects

Choose a location and internal structure for a future Codex project, including focused projects and umbrella projects with durable subprojects. Use when creating or planning a new project. Do not move, rename, or normalize existing projects.

WildPigKing/codex-project-skill-manager · 52 tokens

eco-max

Maximum-savings variant of eco - the same frugality rules with a tighter reply budget, for routine chores (rename, small fix, quick lookup, boilerplate). Prefer plain eco for hard or high-stakes work. Works in any language.

sup3x/codex-eco · 53 tokens