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.
npx agentmods add commands/classicchins/compounding-marketing/cm-standupgit 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-standup)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/cm-standup"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-standup.svg" alt="Measured on agentmods" 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.00528 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
cm-standup 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 6d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cm:standup — Marketing Standup
Structured marketing standup for async teams or solo accountability.
What It Does
A focused 5-minute standup format adapted for marketing work. Perfect for async team updates, accountability partners, or self-management.
Process
-
Yesterday's Marketing
- What marketing work shipped yesterday?
- What moved from "in progress" to "done"?
- Any experiments completed?
-
Today's Marketing
- What marketing work starts or continues today?
- What's the deliverable?
- When will it be done?
-
Blockers
- What's slowing you down?
- Waiting on: [assets, approvals, data, decisions]?
- Need help with: [copywriting, design, technical, strategic]?
-
Metrics Check (optional)
- Any metric that changed significantly?
- Anything worth noting for the team?
Output Format
# Marketing Standup — [Date]
## Yesterday
- ✅ [Completed task 1]
- ✅ [Completed task 2]
- 🔄 [Continued work on X]
## Today
- 🎯 [Priority 1] — [ETA/deliverable]
- 📝 [Priority 2] — [ETA/deliverable]
- 💡 [Priority 3] — [ETA/deliverable]
## Blockers
- ⚠️ [Blocker 1] — Waiting on [person/thing]
- ⚠️ [Blocker 2] — Need help with [specific ask]
## Quick Metrics
- [Metric]: [value] ([trend])
When to Use
- Daily team syncs (async or live)
- Solo accountability (morning routine)
- Before focus blocks (clarify what you're doing)
Time Investment
5 minutes
Output
- Clear accountability on yesterday
- Clear commitment for today
- Visible blockers (easier to get help)
Best Practices
- Be specific — "Write homepage copy" not "work on website"
- Include deliverables — "Draft ready for review by 3pm"
- Surface blockers early — Don't wait until standup to ask for help
- Keep it short — This isn't a status report, it's a pulse check
Philosophy
The standup is a forcing function for clarity. If you can't articulate what you did, what you'll do, and what's blocking you — you don't have clarity. Fix that before starting work.
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.
- 6d ago First seen · 79 lines · 0 tokens per session scan A c2885c391210
cm-standup is a command published in the GitHub repository classicchins/compounding-marketing (7 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 528 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.