ai-executive-assistant: Skill for Codex

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

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

A planning routine that turns a loose list of ideas or tasks into a time-blocked schedule. Time-blocking means assigning specific tasks to available periods on a calendar.

In plain words
What is it for?
Use it to process a brain dump, meeting notes, or proposed schedule, organize the work, and execute the plan after approval.
Why use it?
It gives unstructured plans a workable order and fits them into the user's existing schedule and task system.

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/cosmo-autom8s/ai-executive-assistant/source-command-ea-plan-schedule"><img src="https://agentmods.dev/badge/skills/cosmo-autom8s/ai-executive-assistant/source-command-ea-plan-schedule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,412 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.00022 $0.01412
Opus 5 $0.00011 $0.00706
Sonnet 5 $0.00004 $0.00282
Haiku 4.5 $0.00002 $0.00141

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

Security

Grade A, and why

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

.agents/skills/source-command-ea-plan-schedule/SKILL.md · 133 lines

How it starts

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

source-command-ea-plan-schedule

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

Command Template

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 ~/.codex/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:

  1. Tasks — anything that sounds like a to-do, action item, or deliverable
  2. Dates — any mentioned deadlines, days, or time references (convert relative dates to absolute)
  3. People — anyone mentioned (clients, team members, collaborators)
  4. Projects — which project(s) these relate to
  5. Dependencies — anything that blocks or is blocked by something else
  6. Context — why this matters, what triggered it

Phase 2: ANALYZE — Figure Out How to Integrate

Pull current state

  1. Read <data_dir>/today.md — what's already planned for today?
  2. Read <data_dir>/weekly-plan.md — what's the current week look like?
  3. Read <data_dir>/monthly-goals.md — do these tasks align with goals?
  4. Read <data_dir>/waiting-on.md — any overlap with things already tracked?
  5. Read <data_dir>/task-cache.md — check for duplicate tasks

Read the full file on GitHub · 133 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. 9d ago First seen · 133 lines · 22 tokens per session scan A 6497d5f23363

Subscribe to this mod's changes

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