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/onebrain-ai/onebrain/weeklynpx skills add onebrain-ai/onebrain --skill weeklygit clone --depth 1 https://github.com/onebrain-ai/onebrainWhat 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.00075 | $0.01426 |
| Opus 5 | $0.00037 | $0.00713 |
| Sonnet 5 | $0.00015 | $0.00285 |
| Haiku 4.5 | $0.00007 | $0.00143 |
Grade A, and why
weekly 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 3d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Reflection
Review your week, surface patterns, and set intentions for the week ahead.
Best run on Friday afternoon or over the weekend.
Step 1: Identify This Week's Sessions
Determine the current week's date range (Mon–Sun).
List all session log files in [logs_folder]/session/**/*-session-*.md from this week (post-v2.4.0: session logs live under the dedicated session/ subfolder). If there are none, check the past 7 days. The -session-* infix is no longer strictly required since session/ only contains session logs, but kept as defense-in-depth.
Report:
I found N sessions this week:
- Mon (3/18): session-01 : [topic]
- Wed (3/20): session-01, session-02 : [topics]
- Fri (3/22): session-01 : [topic]
Step 2: Read All Session Logs
Read each session log from this week. Extract:
- Topics worked on
- Decisions made
- Tasks created vs completed
- Insights noted
- Open questions
Step 3: Surface Patterns
Look for:
| Pattern Type | Examples |
|---|---|
| Focus areas | "You spent most of your time on [topic]" |
| Progress made | "You completed X tasks, advanced [project]" |
| Stuck points | "You revisited [problem] 3 times without resolution" |
| Energy patterns | "Most productive sessions were in the morning" |
| Neglected areas | "You haven't touched [goal] this week" |
| Emerging interests | "You captured 4 notes about [new topic]" |
Step 4: Present Weekly Summary
Say:
────────────────────────────────────────────────────────────── 📅 Week of {Mon DD Mon} : {Sun DD Mon YYYY} ────────────────────────────────────────────────────────────── Sessions: {N} total Main focus: {primary topic}
What you worked on: • {Project/topic 1} : {brief status} • {Project/topic 2} : {brief status}
Wins this week: • {Something completed or progressed}
Patterns I noticed: • {Pattern 1} • {Pattern 2}
Open threads: • {Unresolved item}
Step 5: Reflection Questions
Ask (pick 2-3 based on context):
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.
- 3d ago First seen · 189 lines · 75 tokens per session scan A a06a9cdb32b9
weekly is a skill published in the GitHub repository onebrain-ai/onebrain (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,426 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-30.
Other skills, from other repositories
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
priority-dashboard
Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
gws-obsidian-prep
Cross-skill recipe: fetch today's (or tomorrow's) Google Calendar events via gws CLI and create meeting prep notes in the Obsidian vault.
task-manager
Use this when {{username}} or an agent wants to add, review, prioritize, complete, defer, park, or inspect todos, open loops, confirmed actions, waiting states, or attention triggers. Maintains atomic records under operations/actions/ and operations/attention-triggers/ as the only local action truth. Do NOT use for…
obsidian
Obsidian vault management — create notes, backlinks, tags, and Dataview queries via file operations.