close

A session-closing skill that records the work, updates relevant project documentation, and commits and pushes the changes.

In plain words
What is it for?
It helps close implementation or specification work, run an audit for substantial ad-hoc changes, write a journal entry, and update project READMEs.
Why use it?
It prevents a session from ending with only a code commit and no written record of the decisions made.

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/ashkaan/contextium/close
Any agent
npx skills add Ashkaan/contextium --skill close
Clone the repo
git clone --depth 1 https://github.com/Ashkaan/contextium

Made for: Claude Code, Codex.

Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,362 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.00121 $0.03362
Opus 5 $0.00060 $0.01681
Sonnet 5 $0.00024 $0.00672
Haiku 4.5 $0.00012 $0.00336

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

Security

Grade A, and why

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 2d ago.

The scan reads SKILL.md. This mod also ships 12 executable files (scripts/close-fired.sh, scripts/close-fired.test.sh, scripts/detect-mode.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

templates/claude/skills/close/SKILL.md · 242 lines

How it starts

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

/close — Session Wrap

The "wrap" verb of the loop. A session isn't closed by git commit alone — the journal entry is load-bearing. /close writes the journal, updates any touched project README, commits, and pushes, in one pass. For substantial changes that weren't already reviewed by /implement, it runs /implement-audit first so blind spots get caught before the work is sealed.

/close is also the auto-tail of the producer verbs. /spec and /implement auto-invoke /close on clean completion per references/auto-close-gate.md — so in the normal loop nobody types /close; the producing verb fires it. When auto-invoked, the close-fired session marker (scripts/close-fired.sh) guards against a double-fire if a held question resumes the verb after /close had already started. Typing /close yourself still works for ad-hoc sessions that didn't run a producer verb.

Critical

  • The journal is required. Do not stop after git commit. The journal entry (§2) is what makes a past decision reconstructable later per @rule:journal-format; the commit alone is not "closed."
  • Audit substantial ad-hoc changes — and only those. §1 asks a marker file whether this session was already audited. If it was, the review does not run again and its trailer rides onto the commit instead. If it wasn't, and the session changed real code, /implement-audit runs here and every ready finding is fixed before the commit. Do not skip it to close faster.
  • Land the full scope. Fix the audit findings this session per @rule:no-deferral; don't stage them in a README as "follow-ups."

code-review — pre-close audit (substantial ad-hoc changes only)

/implement-audit is the loop's single code reviewer, normally fired by /implement. /close is the backstop for substantial work done OUTSIDE /implement — a quick fix that grew, a refactor you did by hand.

Ask the marker, don't judge it:

bash .claude/skills/implement-audit/scripts/audit-dedupe.sh status

Read the full file on GitHub · 242 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. 2d ago First seen · 242 lines · 121 tokens per session scan A c2b9693e8bc0

Subscribe to this mod's changes

close is a skill published in the GitHub repository Ashkaan/contextium (32 stars, last pushed 5d ago), licensed MIT. It adds 121 tokens to every session and 3,362 once invoked, about $0.0006 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.