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/open-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/open-day)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/open-day"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/open-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.00025 | $0.00375 |
| Opus 5 | $0.00013 | $0.00187 |
| Sonnet 5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
open-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
Run the open-day kickoff:
- Read
dashboards/HOME.mdfor current dashboard state - Read
brain/NORTH_STAR.mdfor current goals - Check
work/INDEX.mdfor active projects - Read yesterday's and today's daily notes if they exist:
obsidian daily:read - List open tasks:
obsidian tasks daily todo - Check recent git activity:
git log --oneline --since="24 hours ago" --no-merges - Check for any unlinked notes or inbox items needing processing
Present a structured open-day summary:
- Yesterday: What got done (from git log and daily note)
- Active Work: Current projects in work/01_PROJECTS/ with their status
- Open Tasks: Pending items
- North Star Alignment: How active work maps to current goals
- Suggested Focus: What to prioritize today based on goals + open items
Keep it concise. This is a quick orientation, not a deep dive.
Daily Note (morning-checkin)
After the open-day summary, run the morning-checkin workflow from the daily-rituals skill:
- Check for an active week in
plan/(show week goal + progress if found) - Check if today's daily note exists (
plan/DD-MM-YY-XX.md) — create from template if not - Ask for today's top 1-3 focus areas
- Mark selected tasks
[/]in source project files and active week file - Fill "Today's Focus" section in the daily note
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 · 35 lines · 25 tokens per session scan A 4e1f25674445
open-day is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 375 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-30.
Other commands, from other repositories
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
om-self-review
Write your self-assessment for your company's review tool. Produces project impact descriptions, competency self-assessments (current level / next level), principles, and growth plan — all within character limits, fact-checked, strategically calibrated.
om-tidy
Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits oversized notes, reports stale open loops, fixes links. Safe by construction: never deletes, never commits, zero content loss.
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-meeting
Prep for any meeting by topic — subject-forward briefing with open tasks, blockers, and brainstormed considerations the user may not have thought of yet.
om-capture-1on1
Take a meeting transcript, notes, or Gemini summary and create a structured vault note with key takeaways, quotes, action items, and DM context.