agentmods.dev

personal-os: Command for Claude Code

.claude/commands/weekly.md

weekly is a command for Claude Code from vmarcondes-nilo/personal-os. It costs 0 tokens per session (865 once invoked), scanned A, original, MIT.

A guided weekly review command that reads your journal, goals, inbox, and area files, then leads a conversation about the past week.

In plain words
What is it for?
Use it to summarize the week, review commitments, spot patterns, rate areas such as work and health, and discuss priorities for the next week.
Why use it?
It gathers scattered notes and commitments into one review, helping you see what happened, what was missed, and what needs attention.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is vmarcondes-nilo/personal-os's own configuration. It tells Claude Code how to work on personal-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything personal-os configures →

not rated 46repo +1 7mo ago A scan 0 tokens original MIT
View source ↗ vmarcondes-nilo/personal-os
Reuse

Borrowing it

Nothing to install: this file belongs to vmarcondes-nilo/personal-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vmarcondes-nilo/personal-os/main/.claude/commands/weekly.md
Clone the repo
git clone --depth 1 https://github.com/vmarcondes-nilo/personal-os

Made for: Claude Code.

Wrote 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.

agentmods badge for weekly

README.md
[![agentmods](https://agentmods.dev/badge/commands/vmarcondes-nilo/personal-os/weekly/github.svg)](https://agentmods.dev/commands/vmarcondes-nilo/personal-os/weekly)
Your own site
<a href="https://agentmods.dev/commands/vmarcondes-nilo/personal-os/weekly"><img src="https://agentmods.dev/badge/commands/vmarcondes-nilo/personal-os/weekly/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for weekly

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 865 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00865
Opus 5.5 $0.00000 $0.00346
Sonnet 5.5 $0.00000 $0.00173
Haiku 4.5 $0.00000 $0.00086

Measured 2mo ago against content hash ee0d1d3fc1de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/weekly.md · 126 lines

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

Read the full file on GitHub · 126 lines

Changes

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.

  1. 2mo ago First seen · 126 lines · 0 tokens per session scan A ee0d1d3fc1de

Subscribe to this mod's changes

weekly is a command published in the GitHub repository vmarcondes-nilo/personal-os (46 stars, last pushed 7mo 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.

PlanningProductivity
Related

weekly compared with commands from other repositories

weekly next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
weeklyvmarcondes-nilo/personal-osCommand467mo agoMITA0Claude Code
wsdanielmiessler/LifeOSCommand20kyesterdayMITA0Claude Code
cancel-ralphanthropics/claude-plugins-officialCommand46kyesterdayApache-2.0A4Claude Code
engage.actionshypnguyen1209/offensive-claudeCommand41215d agoMITA11Claude Code
focusData-Wise/claude-pluginsCommand7yesterdayMITA0Claude Code
stuckData-Wise/claude-pluginsCommand7yesterdayMITA0Claude Code
quickstartorq-ai/assistant-pluginsCommand62d agoMITA23Claude Code