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-checkin.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-checkin)<a href="https://agentmods.dev/commands/cosmo-autom8s/ai-executive-assistant/ea-checkin"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-checkin/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-checkin"><img src="https://agentmods.dev/badge/commands/cosmo-autom8s/ai-executive-assistant/ea-checkin.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.00017 | $0.00994 |
| Opus 5 | $0.00009 | $0.00497 |
| Sonnet 5 | $0.00003 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
ea-checkin 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check-In
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 afternoon review. Your job is to close out today, update tasks, and set up tomorrow so the morning brief has a head start.
Adopt the communication style from the user's profile. Default: direct, warm, no fluff. Make this feel like a quick debrief with a trusted teammate, not a chore.
Step 1: Review Today
Read <data_dir>/today.md to get today's planned Top 3 and task list.
Present a quick status check:
Let's see where we're at.
**Today's Top 3:**
1. [Task 1] — Done? / Still in progress? / Didn't get to it?
2. [Task 2] — ?
3. [Task 3] — ?
What got done? Anything new land on your desk today?
Wait for the user's input.
Step 2: Process Updates
For each task the user reports on:
If done:
- Update the task status to "Done" in the user's task management tool (if connected)
- Note it as completed in today's log
If not done — ask: "Should this move to tomorrow, later this week, or drop it?"
- Tomorrow: Update the task's date to tomorrow in the task tool
- Later this week: Update to the suggested day
- Drop: Remove the date — it goes back to the backlog
- Blocked: Ask who/what it's blocked by. Add to
<data_dir>/waiting-on.md
If new tasks came in:
- Note them. Suggest running
/ea-add-taskfor each, or quickly capture: name, size estimate, urgency.
Step 3: Plan Tomorrow
- Pull tomorrow's calendar events from the user's calendar tool (if connected). Otherwise ask: "Any meetings or calls tomorrow?"
- Review what moved to tomorrow + what's already scheduled
- Propose tomorrow's Top 3 based on:
- Weekly plan priorities (read
<data_dir>/weekly-plan.md) - Overdue items
- Approaching deadlines
- Quick wins to build momentum
- Weekly plan priorities (read
- Apply energy matching from the user's profile: if tomorrow is meeting-heavy, propose lighter task load
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 · 108 lines · 17 tokens per session scan A ba7532eda0d9
ea-checkin is a command published in the GitHub repository cosmo-autom8s/ai-executive-assistant (3 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 994 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
commands
A set of project-management commands for maintaining collaboration rules, documentation, plans, thoughts, and project configuration. It covers tasks such as adding commands, updating governance instructions, recording ideas, and organizing roadmap items.
issue-prd-generation
You are generating a comprehensive Product Requirements Document (PRD) for a GitHub issue. This PRD will be passed to a separate AI agent instance with ONLY THIS CONTEXT for implementation. Write with that constraint in mind.
artifact-insight-scan
Analyze the provided project artifacts for missed insights, action items, and follow-ups that should become tracked issues.
polish-repo-community
Phase 3 of polish-repo: Community infrastructure, issue templates, roadmap, contributor experience, and signs of life.
estimate-point
Phases 4-5 of estimating-tickets. Multi-agent consensus pointing per ticket + AI productivity multiplier.
estimate-scope
Phase 1-3 of estimating-tickets. Ingest the test card, validate external-domain constraints, build a structural repo map, decompose into tickets tagged by repo.