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.
/plugin marketplace add organvm-iv-taxis/a-i--skills/plugin install example-skillsWrote 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/organvm-iv-taxis/a-i--skills/closeout)<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.
<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>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.00133 | $0.01842 |
| Opus 5 | $0.00067 | $0.00921 |
| Sonnet 5 | $0.00027 | $0.00368 |
| Haiku 4.5 | $0.00013 | $0.00184 |
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.
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-NNNreference. No action. - IN-PROGRESS: contains
IRF-XXX-NNNreference 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/*.txtshould be empty)
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.
- 12d ago First seen · 171 lines · 133 tokens per session scan A 735fd08084eb
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.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts.
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.