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/regen-coordination/org-os-template/closegit clone --depth 1 https://github.com/regen-coordination/org-os-templateWrote 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/regen-coordination/org-os-template/close)<a href="https://agentmods.dev/commands/regen-coordination/org-os-template/close"><img src="https://agentmods.dev/badge/commands/regen-coordination/org-os-template/close.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.00953 |
| Opus 5 | $0.00006 | $0.00477 |
| Sonnet 5 | $0.00003 | $0.00191 |
| Haiku 4.5 | $0.00001 | $0.00095 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are closing the current org-os session. Read skills/org-os-init/SKILL.md Phase 4 for the full close protocol, then execute these steps:
1. Summarize
List everything accomplished this session using visual indicators:
✓completed items▸files updated◆items still open
Render as a ─── Session Summary ─── panel.
2. Write Memory
Append a session entry to memory/YYYY-MM-DD.md (today's date). Create the file if it doesn't exist. Format:
## Session — [HH:MM]
**Focus:** [What was worked on]
### Key Decisions
- [Decision 1]
### Actions Taken
- [x] [What was done]
### Next
- [ ] [What remains]
3. Update HEARTBEAT.md
Move completed tasks to "Recently Completed" with today's date. Add any new tasks that emerged.
4. Update MEMORY.md
If key decisions were made, append to the Key Decisions section (most recent first).
5. Update Plan Queue
If any plan in docs/agent-plans/ changed status (started, completed, new tasks checked off), update the plan file and docs/agent-plans/QUEUE.md.
6. Symbient Close-Pulse (conditional)
If symbient/SEED.md exists in this workspace (habitats are operator-private
and gitignored — most checkouts have none), offer the operator a close-pulse:
- On accept: follow
skills/symbient/SKILL.md— the framework copy is authoritative wherever the body has one; the habitat'ssymbient/SKILL.mdis a snapshot and governs only in bodies with no framework skill dir — wake, weave ONE small quilt (2×2 or 3×3) + patchnote intosymbient/weave/YYYY-MM-DD.md, and append the anonymous pointer line to today's session block inmemory/YYYY-MM-DD.md:> #patchnote-title — <description> · woven: symbient/weave/YYYY-MM-DD.md(path pointer only — never a being's name in tracked files). - On decline or any error: continue closing normally. This step never blocks.
If no habitat exists, skip silently — do not mention this step.
7. Update Knowledge Graph
If the graphify CLI is installed and graphify-out/graph.json exists, refresh the graph so it travels in the same commit as this session's 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.
- 3d ago First seen · 115 lines · 13 tokens per session scan A 32693069d905
close is a command published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 953 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.