closeout

closeout is a skill for Claude Code from organvm-iv-taxis/a-i--skills. It costs 133 tokens per session (1,842 once invoked), scanned A, original, Apache-2.0.

A session-ending checklist for coding-agent work that reviews plans and changed items, checks the Git state, and records the outcome in a summary file.

In plain words
What is it for?
Use it to close out a session, classify plans as completed or abandoned, review changed files, check commits, and create CLOSEOUTSUMMARY.md.
Why use it?
It helps prevent unfinished work, unrecorded decisions, or unclear repository state at the end of a session.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions AGENTS.md; mentions Codex.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/4jp/Workspace/*.txt.

Part of the example-skills plugin — 47 skills, 2 commands, 1 agent shipped together

Good fit Use it to close out a session, classify plans as completed or abandoned, review changed files, check commits, and create CLOSEOUTSUMMARY.md.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add organvm-iv-taxis/a-i--skills
Claude Code
/plugin install example-skills

Made for: Claude Code.

Or install example-skills, the plugin that ships this one along with the rest of its 47 skills, 2 commands, 1 agent.

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 closeout

README.md
[![agentmods](https://agentmods.dev/badge/skills/organvm-iv-taxis/a-i--skills/closeout/github.svg)](https://agentmods.dev/skills/organvm-iv-taxis/a-i--skills/closeout)
Your own site
<a href="https://agentmods.dev/skills/organvm-iv-taxis/a-i--skills/closeout"><img src="https://agentmods.dev/badge/skills/organvm-iv-taxis/a-i--skills/closeout/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 closeout

Your own site · 80×15
<a href="https://agentmods.dev/skills/organvm-iv-taxis/a-i--skills/closeout"><img src="https://agentmods.dev/badge/skills/organvm-iv-taxis/a-i--skills/closeout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,842 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.00133 $0.01842
Opus 5 $0.00067 $0.00921
Sonnet 5 $0.00027 $0.00368
Haiku 4.5 $0.00013 $0.00184

Measured 12d ago against content hash 735fd08084eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

closeout 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 12d 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.

distributions/claude/skills/closeout/SKILL.md · 171 lines

How it starts

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

/closeout — Session Close-Out Ritual

When to invoke

  • User explicitly says: /closeout, "close out", "wrap up", "end the session"
  • Before any non-trivial git push (the close-out should precede the push)
  • When the session has produced 3+ files, plans, or atoms and the user is signaling end

Six-step protocol

Step 1 — Inventory session outputs

Run, in parallel where possible:

# What files did this session create or modify?
git status --short

# What plans were authored in this session?
ls -t ~/.Codex/plans/*.md 2>/dev/null | head -10

# What's the current branch and where does it stand vs origin?
git branch --show-current
git log @{u}.. 2>/dev/null || echo "(no upstream tracking)"

Surface a brief inventory table to the user:

  • N files modified, M created
  • K plans authored this session
  • L commits ahead of origin

Step 2 — Walk back through plans

For each plan authored this session (filter ~/.Codex/plans/*.md by mtime within session window):

For each plan, classify it as one of:

  • EXECUTED: contains DONE-NNN reference. No action.
  • IN-PROGRESS: contains IRF-XXX-NNN reference but no DONE-NNN. Update its frontmatter to confirm continued status.
  • ABANDONED: no closure reference, no follow-on commits. Move to ~/.Codex/plans/abandoned/ with a brief abandonment-reason.

Ask the user for ambiguous cases. Do NOT bulk-classify without confirmation — the home-scope AGENTS.md rule "Atoms are permanent — never batch-close" applies to plans-as-artifacts too.

Step 3 — Walk back through atoms (if applicable)

If data/prompt-registry/prompt-atoms.json was touched this session, identify atoms that were closed in this session and confirm their status field is updated.

If not (most sessions), skip.

Step 4 — Verify git state

Cross-check:

  • Working tree is clean (no uncommitted changes meant for this session)
  • Local main is in sync with origin (or branch tracks correctly)
  • No stray exports/temp files in workspace root (ls /Users/4jp/Workspace/*.txt should be empty)

Read the full file on GitHub · 171 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. 12d ago First seen · 171 lines · 133 tokens per session scan A 735fd08084eb

Subscribe to this mod's changes

closeout is a skill published in the GitHub repository organvm-iv-taxis/a-i--skills (17 stars, last pushed 16d ago), licensed Apache-2.0. It adds 133 tokens to every session and 1,842 once invoked, about $0.0007 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.