ai-executive-assistant: Skill for Codex

.agents/skills/source-command-ea-weekly-plan/SKILL.md

source-command-ea-weekly-plan is a skill for Codex from cosmo-autom8s/ai-executive-assistant. It costs 24 tokens per session (1,984 once invoked), scanned A, original, MIT.

A Monday planning routine for setting goals and assigning tasks across the week. It considers calendar commitments and available work time.

In plain words
What is it for?
Use it to review the week's calendar, calculate available hours, define a weekly goal, and place tasks into daily time slots.
Why use it?
It helps compare planned work with real capacity, including meeting time and focused work time.

Skill for Codex

Written for Codex: reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions Claude Code; installed under .agents/ (shared by several agents).

This is cosmo-autom8s/ai-executive-assistant's own configuration. It tells 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/.agents/skills/source-command-ea-weekly-plan/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/cosmo-autom8s/ai-executive-assistant

Made for: 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 source-command-ea-weekly-plan

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

agentmods 80×15 button for source-command-ea-weekly-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/cosmo-autom8s/ai-executive-assistant/source-command-ea-weekly-plan"><img src="https://agentmods.dev/badge/skills/cosmo-autom8s/ai-executive-assistant/source-command-ea-weekly-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,984 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.00024 $0.01984
Opus 5 $0.00012 $0.00992
Sonnet 5 $0.00005 $0.00397
Haiku 4.5 $0.00002 $0.00198

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

Security

Grade A, and why

source-command-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.

.agents/skills/source-command-ea-weekly-plan/SKILL.md · 188 lines

How it starts

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

source-command-ea-weekly-plan

Use this skill when the user asks to run the migrated source command ea-weekly-plan.

Command Template

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 ~/.codex/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.md first. 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.md and 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.

Read the full file on GitHub · 188 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. 10d ago First seen · 188 lines · 24 tokens per session scan A ae5ff2afaf9b

Subscribe to this mod's changes

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