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/railly/agent-brain/morninggit clone --depth 1 https://github.com/Railly/agent-brainWhat 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.00012 | $0.00471 |
| Opus 5 | $0.00006 | $0.00235 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
morning 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 2d 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
Morning brain shouldn't decide priorities. Systems decide. This command curates everything into one focused view.
WAVE 0: Gather Data (ALL PARALLEL)
| # | Tool | Call | Purpose |
|---|---|---|---|
| 1 | Read | 02_Journal/daily/{YESTERDAY}.md |
Carry-over tasks from "## Tomorrow" section |
| 2 | Read | 02_Journal/weekly/week-{YEAR}-W{WEEK_NUM}.md |
MITs + weekly goal |
| 3 | Grep | priority: [12] in 05_Areas/content-creation/ideas/ |
High-priority content ideas |
| 4 | Glob | 01_Inbox/*.md |
Count unprocessed inbox clips |
Compute dates mentally (you know today's date from system context).
WAVE 1: Optional Integrations (PARALLEL)
Only run these if the tools are available:
| # | Tool | When | Purpose |
|---|---|---|---|
| 1 | Calendar integration | If configured | Today's events |
| 2 | Filesystem search | ~/Programming/**/.git (maxdepth 3) |
Discover local repos for activity check |
WAVE 2: Render (NO tool calls)
Combine all results:
# Morning Focus - {WEEKDAY}, {TODAY}
## Today's Calendar
{events if calendar available, or "No calendar configured"}
## Must Do (from yesterday)
{tasks from "Tomorrow" section, or "No carry-over" if empty}
## Weekly MITs Progress
{numbered MITs with completion status}
## Creative Opportunities
{top 2-3 content ideas from grep}
Inbox: {n} clips pending
## Suggested Focus Order
1. Morning: {highest priority task}
2. Midday: {deep work}
3. Afternoon: {creative/content}
Rules
- Terminal output ONLY. No file creation.
- Skip sections with no data rather than showing "N/A"
- Keep it scannable, this should take 30 seconds to read
- Do NOT add intermediate messages between waves
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.
- 2d ago First seen · 60 lines · 12 tokens per session scan A 8fec7d021d1e
morning is a command published in the GitHub repository Railly/agent-brain (22 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 471 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.