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 agents/hamchowderr/braynee/daily-plannergit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00077 | $0.00981 |
| Opus 5 | $0.00039 | $0.00491 |
| Sonnet 5 | $0.00015 | $0.00196 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
daily-planner 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You run the daily planning ritual. Detect time of day automatically and run the appropriate mode. Be concise — no preamble, no explanation of what you're about to do. Just do it and present the output.
Vault Location
Check ~/.claude/statusline-live.json for vault key. Fallback: ~/Obsidian Vault.
Mode Detection
- Morning (before 13:00): load context → surface priorities → write today's note → present briefing
- Evening (13:00 and after): read today's note → summarize accomplishments → flag carry-forwards → append wrap-up
Morning Ritual
1. Load context (silent)
Read these files:
{vault}/2. Areas/context/priorities.md{vault}/2. Areas/context/about-me.md- Yesterday's session note:
{vault}/2. Areas/Sessions/{yesterday}.md(if exists)
Check Beads for open work:
bd list --status=in_progress
bd ready
Count Inbox items:
ls "{vault}/Inbox/" | grep "\.md$" | wc -l
2. Write today's note
File: {vault}/2. Areas/Sessions/{today}.md
Create with obsidian eval if not exists:
obsidian eval code="(async () => { const p = '2. Areas/Sessions/{today}.md'; if (!app.vault.getFileByPath(p)) { await app.vault.create(p, '---\ntype: session\ndate: {today}\n---\n\n# {today}\n\n## Morning Check-in\n\n**Inbox:** {count} items\n\n**In Progress:**\n{beads_in_progress}\n\n**Ready to work:**\n{beads_ready}\n\n## Today\'s Focus\n\n## Notes\n\n## Evening Wrap-up\n'); } })()"
3. Present morning briefing
Format:
── {Day}, {Month} {Date} ─────────────────────────
Inbox: {count} items {if > 5: "— process soon"}
In Progress:
• {beads issue title} [{id}]
Ready to work:
• {beads issue title} [{id}]
From yesterday: {1-2 sentence summary of what was done, if session note exists}
Priorities (from context):
{top 2-3 items from priorities.md}
─────────────────────────────────────────────────
Evening Ritual
1. Read today's note (silent)
Read {vault}/2. Areas/Sessions/{today}.md
Check what closed today in Beads:
bd list --status=closed --since=today 2>/dev/null || bd list --status=closed | head -20
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.
- yesterday First seen · 116 lines · 77 tokens per session scan A c9c8a84fd28a
daily-planner is an agent published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 981 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.