personal-os: Command for Claude Code

.claude/commands/review.md

review is a command for Claude Code from jordantcarlisle/personal-os. It costs 0 tokens per session (508 once invoked), scanned A, original, MIT.

A weekly personal-work review command based on Getting Things Done, a method for collecting tasks and deciding their next action.

In plain words
What is it for?
Use it to process open tasks, review projects and responsibilities, inspect calendar follow-ups, and plan the coming week.
Why use it?
It helps clear the inbox, find stalled projects, check commitments, and keep plans current in one scheduled review.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is jordantcarlisle/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 →

Reuse

Borrowing it

Nothing to install: this file belongs to jordantcarlisle/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/jordantcarlisle/personal-os/main/.claude/commands/review.md
Clone the repo
git clone --depth 1 https://github.com/jordantcarlisle/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 review

README.md
[![agentmods](https://agentmods.dev/badge/commands/jordantcarlisle/personal-os/review/github.svg)](https://agentmods.dev/commands/jordantcarlisle/personal-os/review)
Your own site
<a href="https://agentmods.dev/commands/jordantcarlisle/personal-os/review"><img src="https://agentmods.dev/badge/commands/jordantcarlisle/personal-os/review/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 review

Your own site · 80×15
<a href="https://agentmods.dev/commands/jordantcarlisle/personal-os/review"><img src="https://agentmods.dev/badge/commands/jordantcarlisle/personal-os/review.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 508 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.00508
Opus 5 $0.00000 $0.00254
Sonnet 5 $0.00000 $0.00102
Haiku 4.5 $0.00000 $0.00051

Measured 11d ago against content hash 6c3717e6bb8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

review 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 11d 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/review.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Chief of Staff — Weekly Review

The most important ritual in the system. Walk through it systematically.

Before Starting

Block 60-90 minutes. This is not a quick check-in. Read 00-cockpit/weekly-review.md for the full template.

Part 1: Get Clear (20 min)

  1. Process inbox to zero: Read every item in 00-cockpit/inbox.md. For each, walk through the GTD processing checklist. Every item gets a destination — nothing stays.

  2. Mind sweep: Ask prompting questions to surface open loops:

    • "Anything you told someone you'd do this week?"
    • "Anything nagging at the back of your mind?"
    • "Any commitments from meetings this week?"
    • "Any personal errands or tasks you've been avoiding?" Capture all new items to inbox, then process them too.
  3. Calendar review: Review this week's past events for follow-ups. Check next week for prep needs.

Part 2: Get Current (20 min)

  1. Review every active project in 01-projects/:

    • Does it have a clear next action? If not, define one now.
    • Is it stalled? Kill, pause, or pivot?
    • Is the status field accurate?
    • Update the Active Projects Radar on dashboard.
  2. Review areas in 02-areas/: Any neglected? Any consuming too much time?

  3. Review Waiting For on dashboard: Flag anything >2 weeks. Suggest follow-ups. Remove resolved items.

  4. Review Someday/Maybe (if exists): Anything to activate? Delete?

Part 3: Get Creative (15 min)

  1. Reflect:

    • "What was your biggest win this week?"
    • "What was the biggest lesson?"
    • "What went well that you should keep doing?"
    • "What didn't work that you should change?"
  2. Happiness check: "On a scale of 1-10, how happy were you this week? Why?"

Part 4: Commit (15 min)

  1. Non-negotiables for next week (max 3)
  2. Say NO: What will you actively decline or defer?
  3. Weekly theme: One phrase capturing next week's focus
  4. Update dashboard for Monday
  5. Save: Run /save to commit and push all changes

Read the full file on GitHub · 53 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. 11d ago First seen · 53 lines · 0 tokens per session scan A 6c3717e6bb8e

Subscribe to this mod's changes

review is a command published in the GitHub repository jordantcarlisle/personal-os (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 508 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-31.