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 agentmods add commands/irachrist1/claude-code-workflow-os/closeoutgit clone --depth 1 https://github.com/irachrist1/claude-code-workflow-osWrote 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/commands/irachrist1/claude-code-workflow-os/closeout)<a href="https://agentmods.dev/commands/irachrist1/claude-code-workflow-os/closeout"><img src="https://agentmods.dev/badge/commands/irachrist1/claude-code-workflow-os/closeout.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00193 |
| Opus 5 | $0.00006 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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 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.
What it actually says
Closeout
Close out the current task loop.
Required behavior
- Run the same standard as
/workflow-starter:ship-check. - If the task is complete:
- mark the task status clearly in
context/todo.md - sync the relevant project memory
- mark the task status clearly in
- If the task is not complete:
- create a handoff using the same standard as
/memory-handoff:capture - update
context/todo.mdwith the next concrete step
- create a handoff using the same standard as
- Return a final status:
- complete
- partial with handoff
- blocked
Rules
- Never mark work complete without verification.
- If blocked, say exactly what is blocking progress.
- If partial, leave the next session a clean starting point.
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.
- 3d ago First seen · 30 lines · 13 tokens per session scan A 3051a0e7fe1d
closeout is a command published in the GitHub repository irachrist1/claude-code-workflow-os (2 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 193 once invoked, about $0.0001 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.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.