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.
git clone --depth 1 https://github.com/classicchins/compounding-marketingWrote 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/classicchins/compounding-marketing/cm-daily)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/cm-daily"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-daily/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/classicchins/compounding-marketing/cm-daily"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-daily.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.00000 | $0.00467 |
| Opus 5.5 | $0.00000 | $0.00187 |
| Sonnet 5.5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
cm-daily 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 2mo 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.
What it actually says
/cm:daily — Daily Marketing Review
Quick daily check-in on marketing performance and priorities.
What It Does
A 10-minute daily review that keeps you informed on what's live, what's working, and what needs attention — without getting lost in dashboards.
Process
-
What's Live Today
- Ask: What campaigns, content, or experiments are currently active?
- Check: Any new content published in last 24h?
- Check: Any ads running?
- Check: Any email sequences active?
-
Performance Snapshot
- Ask: What metrics moved yesterday? (Traffic, signups, trials, MRR)
- Ask: Any notable wins? (Viral post, PR mention, ranking improvement)
- Ask: Any red flags? (Ad spend issues, conversion drops, negative feedback)
-
Attention Required
- What needs action today?
- Any time-sensitive opportunities?
- Any fires to put out?
-
Today's Marketing Focus
- Ask: What's the ONE most important marketing task today?
- Ask: What would make today a marketing win?
Output Format
# Daily Marketing Review — [Date]
## What's Live
- **Campaigns:** [Active campaigns/ads]
- **Content:** [Recently published]
- **Sequences:** [Active email flows]
## Performance Snapshot
- **Traffic:** [trend vs yesterday/last week]
- **Signups:** [count + trend]
- **Key metric:** [whatever matters most]
## Wins
- [Notable positive signal]
## Flags
- [Anything concerning]
## Today's Focus
1. **Priority:** [The ONE thing]
2. **Quick wins:** [Optional 2-3 small tasks]
## Notes
- [Anything to remember]
When to Use
- Start of each workday (before diving into tasks)
- After a launch (daily during launch week)
- When managing multiple campaigns
Time Investment
10-15 minutes
Output
- Quick mental model of marketing state
- Clear priority for the day
- Early warning on problems
Philosophy
Daily awareness prevents surprises. The goal isn't deep analysis — it's staying oriented. Save deep dives for /cm:weekly.
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.
- 2mo ago First seen · 79 lines · 0 tokens per session scan A 7b3104397abd
cm-daily is a command published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 467 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.
cm-daily compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cm-dailyclassicchins/compounding-marketing | Command | 8 | 5mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |