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/weekgit 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.00011 | $0.00705 |
| Opus 5 | $0.00005 | $0.00352 |
| Sonnet 5 | $0.00002 | $0.00141 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
week 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create/open weekly plan: $ARGUMENTS
IMPORTANT: Be direct
- Create file if not exists, update if exists
- Week starts Monday
Flow
-
Calculate week dates
- Monday of current week
- File:
02_Journal/weekly/week-YYYY-WXX.md(e.g., week-2026-W02)
-
Fetch calendar events (if calendar integration available) If you have a calendar MCP or integration configured in CLAUDE.md, list events for the week (Mon 00:00 to Sun 23:59).
-
Read health data for this week (optional) If
05_Areas/health/daily/exists, read files for each day (Mon-Sun) of this week. Compute from available days:- avg_sleep = mean of sleep_minutes
- avg_steps = mean of steps
- exercise_days = count of days with exercise_minutes > 0
If
05_Areas/health/weekly/YYYY-WXX.mdexists, read it instead (pre-computed). -
Create weekly plan:
---
type: week
start: YYYY-MM-DD
end: YYYY-MM-DD
---
# Week {N} - {Month} {Year}
## Weekly Goal
{One clear goal for the week - from $ARGUMENTS or ask}
## MITs (Most Important Things)
- [ ] {MIT 1}
- [ ] {MIT 2}
- [ ] {MIT 3}
## Calendar
| Day | Meetings | Deep Work |
|-----|----------|-----------|
| Mon | {count} | {hours}h |
| Tue | {count} | {hours}h |
| Wed | {count} | {hours}h |
| Thu | {count} | {hours}h |
| Fri | {count} | {hours}h |
| Sat | {count} | {hours}h |
| Sun | {count} | {hours}h |
**Key Events This Week:**
- {event 1}
- {event 2}
## Days
| Day | Focus | Status |
|-----|-------|--------|
| Mon [[YYYY-MM-DD]] | | |
| Tue [[YYYY-MM-DD]] | | |
| Wed [[YYYY-MM-DD]] | | |
| Thu [[YYYY-MM-DD]] | | |
| Fri [[YYYY-MM-DD]] | | |
| Sat [[YYYY-MM-DD]] | | |
| Sun [[YYYY-MM-DD]] | | |
## Wins
-
## Learnings
-
## Next Week
-
-
Warn if calendar is packed
- More than 5 meetings/day = warn "heavy meeting day"
- Less than 2h deep work available = warn "no focus time"
- Conflicts with MITs = suggest rescheduling
-
If week exists, show current status:
- MITs progress
- Days completed
- Calendar changes since last view
- Suggest updates
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 · 107 lines · 11 tokens per session scan A d4dc8caf9d4f
week is a command published in the GitHub repository Railly/agent-brain (22 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 705 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.