ai-executive-assistant: Command for Claude Code

.claude/commands/ea-monthly-goals.md

ea-monthly-goals is a command for Claude Code, Codex from cosmo-autom8s/ai-executive-assistant. It costs 18 tokens per session (1,450 once invoked), scanned A, original, MIT.

A monthly planning command that helps choose three focus areas and define how success will be measured. It uses the user's assistant profile, previous goals, work pace, and connected task-management data when available.

In plain words
What is it for?
Use it to review the previous month, identify stalled or deadline-driven projects, assess open tasks, and set three measurable monthly goals.
Why use it?
It reduces scattered priorities by making the user choose what matters this month and explicitly set aside other work.

Command for Claude CodeCodex

Written for Claude Code and Codex: installed under .claude/, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions Claude Code; mentions Codex.

This is cosmo-autom8s/ai-executive-assistant's own configuration. It tells Claude Code and Codex how to work on ai-executive-assistant 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 ai-executive-assistant configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/cosmo-autom8s/ai-executive-assistant/main/.claude/commands/ea-monthly-goals.md
Clone the repo
git clone --depth 1 https://github.com/cosmo-autom8s/ai-executive-assistant

Made for: Claude Code, Codex.

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 ea-monthly-goals

README.md
[![agentmods](https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-monthly-goals/github.svg)](https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-monthly-goals)
Your own site
<a href="https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-monthly-goals"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-monthly-goals/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 ea-monthly-goals

Your own site · 80×15
<a href="https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-monthly-goals"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-monthly-goals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,450 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.00018 $0.01450
Opus 5 $0.00009 $0.00725
Sonnet 5 $0.00004 $0.00290
Haiku 4.5 $0.00002 $0.00145

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

Security

Grade A, and why

ea-monthly-goals 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/ea-monthly-goals.md · 154 lines

How it starts

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

Monthly Goals

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. It's time to set the monthly direction. Your job is to help pick 3 focus areas that actually move the needle — and explicitly park everything else.

Adopt the communication style from the user's profile. Default: strategic, grounding, slightly challenging. Push back on scope creep and scattered priorities. Help commit to less so more gets finished.

Phase 1: INTAKE — Reflect on Last Month

Context Files

  1. Read current <data_dir>/monthly-goals.md — what were last month's goals?
  2. Read <data_dir>/velocity.md — monthly trends and weekly summaries

Tasks & Projects

  1. Pull active projects from the user's task management tool (if connected).
    • Note which projects have deadlines this month, which are stalled.
  2. Pull task volume — how many open tasks exist? How many are orphans (no goal alignment)?
  3. If no task tool is configured, skip and work from context files.

Knowledge Base

  1. Check the user's knowledge base for recent daily notes (last 3-5 days).
    • What's been on their mind? What themes keep coming up?
    • If no knowledge base is configured, skip.

Phase 2: REFLECT — Last Month's Scorecard

Present a quick scorecard of last month:

**Last month's goals:**
1. [Goal 1] — [Achieved / Partially / Missed] — [one-line why]
2. [Goal 2] — [Achieved / Partially / Missed] — [one-line why]
3. [Goal 3] — [Achieved / Partially / Missed] — [one-line why]

**Velocity trend:** [Avg completion rate, overcommit score]
**Pattern:** [Key observation]

If this is the first month (no prior goals), skip the scorecard: "First month — no prior goals to review. Let's set the baseline."

Read the full file on GitHub · 154 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 · 154 lines · 18 tokens per session scan A ed52c72e29a1

Subscribe to this mod's changes

ea-monthly-goals is a command published in the GitHub repository cosmo-autom8s/ai-executive-assistant (3 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 1,450 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.