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 skills/railly/agent-brain/weeknpx skills add Railly/agent-brain --skill 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 skill 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…