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/vmarcondes-nilo/personal-os/weeklygit clone --depth 1 https://github.com/vmarcondes-nilo/personal-osWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/vmarcondes-nilo/personal-os/weekly)<a href="https://agentmods.dev/commands/vmarcondes-nilo/personal-os/weekly"><img src="https://agentmods.dev/badge/commands/vmarcondes-nilo/personal-os/weekly.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.00865 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Review
Run the weekly review. Follow every step below in order. This is a conversational session — don't rush through. Each step involves asking questions and discussing before moving on.
1. Read Context
Read these files to build the week's context:
- All daily journal entries from this week in
journal/daily/(find files from the last 7 days) - Current quarter's OKR file in
goals/ inbox.md— items to process- All area files in
areas/
2. Look Back — Summarize the Week
From the daily journal entries and area files, present a concise summary of the week:
- Key events and accomplishments per area
- Commitments made vs. completed
- Any patterns (e.g., skipped exercise, lots of meetings, inbox piling up)
If there are no daily entries for the week, note that and ask for a verbal recap.
3. Score Each Area
Ask the user to rate each area 1-10 for the week. Present this table:
| Area | Score | Why |
|---|---|---|
| Work | /10 | |
| Relationships | /10 | |
| Health | /10 | |
| Personal Growth | /10 |
After scoring, discuss:
- "Which area needs the most attention next week?"
- Challenge if any score seems off based on what the journal entries show
4. Wins & Gratitude
Ask:
- "What are you most proud of this week?" — push for at least 1 concrete win
- "What are you grateful for?"
Don't skip this even if they're in a rush. Anchoring on wins matters.
5. Lessons & Gaps
Ask:
- "What didn't go well? What fell through the cracks?"
- "What would you do differently?"
- "Any commitments you didn't keep?"
Be direct — if the journal entries show dropped balls, name them.
6. Next Week's Priorities
For each area, set 1-2 priorities for next week:
- Work: What's the #1 thing to move forward?
- Relationships: Who needs your attention?
- Health: What's the exercise/sleep plan?
- Personal Growth: What will you learn or build?
Coaching rules:
- Max 2 per area — push back on overcommitment
- Challenge: are these truly important, or just urgent?
- Check alignment with quarterly OKRs
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.
- 6d ago First seen · 126 lines · 0 tokens per session scan A ee0d1d3fc1de
weekly is a command published in the GitHub repository vmarcondes-nilo/personal-os (43 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 865 tokens. 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
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.