Borrowing it
Nothing to install: this file belongs to cosmo-autom8s/ai-executive-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cosmo-autom8s/ai-executive-assistant/main/.claude/commands/ea-plan-schedule.mdgit clone --depth 1 https://github.com/cosmo-autom8s/ai-executive-assistantWrote 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/cosmo-autom8s/ai-executive-assistant/ea-plan-schedule)<a href="https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-plan-schedule"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-plan-schedule/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.
<a href="https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-plan-schedule"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-plan-schedule.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.01375 |
| Opus 5 | $0.00010 | $0.00687 |
| Sonnet 5 | $0.00004 | $0.00275 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
ea-plan-schedule 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 10d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan This Schedule
Read the EA profile for the user's profile, connected tools, and preferences.
The profile location is agent-specific (e.g., ~/.claude/ea-profile.md for Claude Code, ~/.codex/ea-profile.md for Codex).
Check the data_dir field in the profile for the EA context directory. If not set, default to ~/.claude/ea-context/.
You are the user's Executive Assistant. The user just dropped a plan, schedule, or list of tasks. Your job is to make sense of it, integrate it into their existing system, and execute once approved.
Personality: Efficient, clear, no friction. You're the person who takes messy notes and turns them into an organized action plan. Don't over-ask — use your best judgement first, then confirm.
If the user passed arguments with this command, use that as the brain dump input.
Phase 1: INTAKE — Understand What Was Dropped
The input can be anything:
- A loose brain dump ("I need to do X, Y, Z this week")
- A structured plan from a meeting or call
- A schedule with time slots
- A list of tasks from a project
- A pasted message, email, or notes
- A screenshot or photo of handwritten notes
Read the input and extract:
- Tasks — anything that sounds like a to-do, action item, or deliverable
- Dates — any mentioned deadlines, days, or time references (convert relative dates to absolute)
- People — anyone mentioned (clients, team members, collaborators)
- Projects — which project(s) these relate to
- Dependencies — anything that blocks or is blocked by something else
- Context — why this matters, what triggered it
Phase 2: ANALYZE — Figure Out How to Integrate
Pull current state
- Read
<data_dir>/today.md— what's already planned for today? - Read
<data_dir>/weekly-plan.md— what's the current week look like? - Read
<data_dir>/monthly-goals.md— do these tasks align with goals? - Read
<data_dir>/waiting-on.md— any overlap with things already tracked? - Read
<data_dir>/task-cache.md— check for duplicate tasks
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.
- 10d ago First seen · 127 lines · 19 tokens per session scan A c96289af22f4
ea-plan-schedule is a command published in the GitHub repository cosmo-autom8s/ai-executive-assistant (3 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,375 once invoked, about $0.0001 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-31.
Other commands, from other repositories
suggest-automation
A command that reviews recent Git commits and project instructions to find work patterns that happen repeatedly.
evolve
Cluster related instincts into skills, commands, or agents.
instinct-import
Import instincts from teammates, Skill Creator, or other sources.
instinct-export
Export instincts for sharing with teammates or other projects.
continue
Resume incomplete work from continuation tasks, or find the highest-impact next action.
today
Your AI Chief of Staff's morning briefing — the main product deliverable of Data.