personal-os: Command for Claude Code

.claude/commands/plan.md

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

A daily planning command that creates a realistic plan from your calendar, inbox, projects and current priorities. It limits the day's commitments to the available work time.

In plain words
What is it for?
Use it to choose today's top tasks, account for meetings and breaks, estimate durations, set priorities and define what completion means for each item.
Why use it?
It helps prevent scheduling more focused work than the day can hold and separates urgent tasks from important work that needs protected time.

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/plan.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 plan

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/jordantcarlisle/personal-os/plan"><img src="https://agentmods.dev/badge/commands/jordantcarlisle/personal-os/plan.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 478 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.00478
Opus 5 $0.00000 $0.00239
Sonnet 5 $0.00000 $0.00096
Haiku 4.5 $0.00000 $0.00048

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

Security

Grade A, and why

plan 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 9d 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/plan.md · 46 lines

What it actually says

Chief of Staff — Daily Planning

Build a focused, realistic plan for today. Push back on overcommitment.

Process

  1. Gather inputs (run in parallel):

    • Read 00-cockpit/dashboard.md for current Top 3 and projects radar
    • Check today's calendar for fixed events and available time
    • Read 00-cockpit/inbox.md for unprocessed items that might be urgent
    • Scan 01-projects/ for pending next actions
  2. Calculate available time:

    • Total waking work hours
    • Minus fixed calendar events (meetings, appointments)
    • Minus transition time (15 min between meetings)
    • Minus breaks and meals
    • = Available deep work hours
  3. Prioritize (Eisenhower matrix):

    • Q1 (Urgent + Important): Must do today — schedule first
    • Q2 (Important, Not Urgent): SACRED — protect deep work blocks for this
    • Q3 (Urgent, Not Important): Delegate, batch, or timebox strictly
    • Q4 (Neither): Drop it
  4. Build committed sprint:

    • Maximum 3-5 items
    • Each item: clear definition of done, estimated duration, priority level
    • Total estimated time MUST fit within available hours
    • If it doesn't: "You have [X] hours of meetings and are trying to commit to [Y] hours of deep work. That's [Z] hours over. Pick your top 2-3."
  5. GTD compliance check:

    • Scan every active project in 01-projects/
    • Flag any without a clear next action: "[Project] has no next action — what's the next step?"
  6. Write to dashboard:

    • Update Top 3 on 00-cockpit/dashboard.md
    • Update schedule table with timeboxed items
  7. Timebox onto calendar (if calendar connected):

    • Schedule blocks for each committed item
    • Hard tasks during peak energy hours, admin during trough
    • Leave 15-min buffer between blocks
  8. Confirm: Present the plan. "Does this look right? Anything to adjust?"

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. 9d ago First seen · 46 lines · 0 tokens per session scan A 4587d66fb835

Subscribe to this mod's changes

plan 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 478 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.