cm-eod

A short end-of-day command for recording completed marketing work, unfinished tasks, blockers, and the next day's starting point.

In plain words
What is it for?
Use it to create a daily wrap-up covering shipped work, in-progress items, blockers, tomorrow's first task, and optional notes.
Why use it?
It prevents useful context from being lost and makes it clear what shipped, what still needs attention, and what is delaying progress.

Command

Part of the compounding-marketing plugin — 39 skills, 17 commands shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/classicchins/compounding-marketing/cm-eod
Clone the repo
git clone --depth 1 https://github.com/classicchins/compounding-marketing

Or install compounding-marketing, the plugin that ships this one along with the rest of its 39 skills, 17 commands.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 604 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00604
Opus 5 $0.00000 $0.00302
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00060

Measured 3d ago against content hash 2e702caee8a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cm-eod 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 3d 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.

commands/cm-eod.md · 94 lines

How it starts

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

/cm:eod — End of Day Marketing Wrap

Close out the day with clarity on what shipped and what's next.

What It Does

A 5-10 minute end-of-day ritual that captures what you accomplished, documents blockers, and sets up tomorrow for a fast start.

Process

  1. What Shipped

    • What marketing work was completed today?
    • What moved from draft to published?
    • What went from idea to execution?
    • What experiments concluded?
  2. What's In Progress

    • What's partially done?
    • What's the next step to complete it?
    • When will it ship?
  3. What's Blocked

    • What couldn't you finish and why?
    • Who/what are you waiting on?
    • What decision is needed?
  4. Tomorrow's Setup

    • What's the first marketing task tomorrow?
    • What can you prepare now to start faster?
    • Any context to capture while it's fresh?
  5. Capture Notes (optional)

    • Anything worth remembering?
    • Ideas that came up during the day?
    • Things to research or try?

Output Format

# EOD Marketing Wrap — [Date]

## Shipped ✅
- [Completed item 1]
- [Completed item 2]

## In Progress 🔄
- [Item] — Next step: [action] — ETA: [when]
- [Item] — Next step: [action] — ETA: [when]

## Blocked ⚠️
- [Item] — Waiting on: [person/thing]
- [Item] — Need: [decision/resource]

## Tomorrow's Start
- **First task:** [specific task]
- **Prep done:** [anything set up for fast start]

## Notes
- [Idea captured]
- [Thing to research]
- [Context worth remembering]

When to Use

  • End of each workday
  • Before switching contexts (if marketing is part-time)
  • Before days off (capture everything for smooth return)

Time Investment

5-10 minutes

Output

  • Clear record of daily progress
  • Visible blockers to address
  • Tomorrow ready to start without warmup time

Why EOD > Morning Review

Morning reviews are valuable, but EOD wraps solve a different problem:

  • Context is fresh — You remember details now, not tomorrow morning
  • Blockers surface — You can send an ask before logging off
  • Tomorrow starts fast — No "wait, what was I doing?" friction
  • Separation — Closing ritual helps mentally end the workday

Read the full file on GitHub · 94 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. 3d ago First seen · 94 lines · 0 tokens per session scan A 2e702caee8a0

Subscribe to this mod's changes

cm-eod is a command published in the GitHub repository classicchins/compounding-marketing (7 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 604 tokens. 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.