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.
npx skills add TAKEOFF69/codex-skills-kit --skill session-closegit clone --depth 1 https://github.com/TAKEOFF69/codex-skills-kitWrote 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.
[](https://agentmods.dev/skills/takeoff69/codex-skills-kit/session-close)<a href="https://agentmods.dev/skills/takeoff69/codex-skills-kit/session-close"><img src="https://agentmods.dev/badge/skills/takeoff69/codex-skills-kit/session-close/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.
<a href="https://agentmods.dev/skills/takeoff69/codex-skills-kit/session-close"><img src="https://agentmods.dev/badge/skills/takeoff69/codex-skills-kit/session-close.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.00931 |
| Opus 5.5 | $0.00024 | $0.00372 |
| Sonnet 5.5 | $0.00012 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
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 2mo 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.
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
- Read repository
AGENTS.mdand nested instructions governing changed paths. - Use repository-native closeout, worktree, documentation, and verification commands when defined.
- 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:
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.
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.
- 2mo ago First seen · 137 lines · 59 tokens per session scan A be93dd059792
session-close is a skill published in the GitHub repository TAKEOFF69/codex-skills-kit (8 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 931 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
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.
ledger-tasks-yylo
Durable in-repo task state for coding agents — Kanban tasks with stable IDs, evidence-backed status marks, blocked-by dependencies, and next-ready selection. Use when starting, selecting, sequencing, or closing implementation tasks for a coding-agent project.
documentation
Use when the user asks to install or maintain a documentation index, keep CLAUDE.md or AGENTS.md inventories synchronized with files, add document metadata, classify documentation, or apply documentation-only setup to a repository.
status
Show active or recent Claude Code jobs in this repository, or detailed status for a specific job id. Args: [job-id], --wait, --timeout-ms , --poll-interval-ms , --all. Use for tracked-job inspection, not setup or result retrieval.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
infrastructure-project
Skill for the project management infrastructure module providing multi-project discovery, structure validation, and metadata extraction. Use when discovering active projects, validating project directory structure, or extracting project configuration metadata.