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/superuser-pal/awesome-second-brain/close-daygit clone --depth 1 https://github.com/superuser-pal/awesome-second-brainWrote 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/superuser-pal/awesome-second-brain/close-day)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/close-day"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/close-day.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.00000 | $0.00444 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
close-day 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 5d 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
Close Day
Fast session review and consistency check before ending.
Usage
/close-day
Triggered when the user says "close day", "wrap up", "let's wrap", "wrapping up", or similar. Claude should invoke this automatically.
Workflow
1. Fast Session Review
Scan the conversation for newly created or modified notes:
- List created/modified notes with paths.
- Sanity check: Ensure each new note has at least one wikilink and a
descriptionfield. - Project sync: Update status fields of projects touched this session (e.g.,
active->completed).
2. Update Critical Context
work/INDEX.md— register new notes in "Recent Notes" or "Active Projects".brain/MEMORIES.md— if critical new context was learned, ensure it's linked from the "Recent Context" section.
3. Thinking Notes Clean-up
- Scan
thinking/for unarchived notes withstatus: thinking. If any exist, list them and suggest running/processlater.
4. Ways of Working Reflection
Briefly identify if this session revealed a major new pattern or gotcha for:
brain/RULES.mdbrain/CAVEATS.mdCLAUDE.md(e.g., new project convention)
5. Evening Review (evening-review)
Run the evening-review workflow from the daily-rituals skill:
- Read today's daily note from
plan/. - Mark accomplished tasks
[x]in daily note and project files. - Suggest 1 priority for tomorrow.
- Append the section to the daily note.
6. Report
Present a lean summary:
- Done: notes captured and projects updated.
- Tomorrow: top priority.
- Flagged: anything requiring immediate user action.
Important
- This is a light consistency pass, NOT a full audit. Keep it fast.
- Deep analytical work (wins capture, orphan scans, competency mapping) is deferred to
/week-close.
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.
- 5d ago First seen · 58 lines · 0 tokens per session scan A bc2978411ed0
close-day is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 444 tokens. 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 commands, from other repositories
onboard
Interview-based first-run setup for this LLM Wiki kit. Asks the essential questions (vault location/name, Mode A/B, mothership path, Core Context identity + reuse axes), then fills every placeholder and writes Core Context so the wiki knows you from day one. Activate when the user says "온보딩해줘", "처음 시작할게", "처음 시작"…
refresh-context
Re-snapshot Core Context.md from (optional) mothership system files + key personal essays. Run when mothership files change, when new essays signal philosophy shift, or when snapshot is older than 30 days.
om-vault-upgrade
Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.
om-correct
Sweep a corrected fact through the vault — finds every note restating it, applies the correction at the single source, replaces restatements with links, and preserves notes that correctly record what was believed at the time.
om-intake
Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.
om-prep-1on1
Prep for an upcoming 1:1 — load person context, surface open items, suggest agenda based on vault state.