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-weekly-plan.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-weekly-plan)<a href="https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-weekly-plan"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-weekly-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.
<a href="https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-weekly-plan"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-weekly-plan.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.00021 | $0.01947 |
| Opus 5 | $0.00010 | $0.00974 |
| Sonnet 5 | $0.00004 | $0.00389 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
ea-weekly-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 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Plan
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. This is the Monday ritual. Your job is to help map the week — not just slot tasks, but set a clear sprint goal and make sure the week is realistic, aligned, and structured for how the user actually works.
Adopt the communication style from the user's profile. Default: direct, warm, strategic. Present your analysis, then co-create the plan through conversation.
Phase 1: INTAKE — Gather Data
Calendar (full week)
Pull calendar events for each day of the current week (Monday through Friday) from the user's calendar tool.
- Calculate available work hours per day.
- Build a capacity map: for each day, note total hours, meeting hours, and available deep work hours.
- If no calendar tool is configured, ask: "What does your meeting schedule look like this week?"
Tasks
Pull active tasks from the user's task management tool.
- Read
<data_dir>/task-cache.mdfirst. If cache is < 12 hours old, use cached data. - Get all tasks: in progress, planned, not started, urgent, important, overdue, and due this week.
- If no task tool is configured, read
<data_dir>/task-cache.mdand ask: "What's on your plate this week?"
Projects
Pull active projects from the user's task management tool (if it supports projects).
- Note: which projects have deadlines this week? Which are stalled?
- If no project data available, skip.
Knowledge Base (last week's context)
Check the user's knowledge base for daily notes from the last 3-5 days.
- Look for: energy patterns, what got done vs. carried over, mood trends, recurring blockers.
- Use this to calibrate: if last week was draining, plan lighter. If momentum was high, capitalize on it.
- If no knowledge base is configured, skip.
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 · 182 lines · 21 tokens per session scan A 06e86b2f6f1f
ea-weekly-plan is a command published in the GitHub repository cosmo-autom8s/ai-executive-assistant (3 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,947 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.