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-sprint)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/cm-sprint"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-sprint/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-sprint"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-sprint.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.00901 |
| Opus 5.5 | $0.00000 | $0.00360 |
| Sonnet 5.5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
cm-sprint 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cm:sprint — Marketing Sprint Planning
Plan a focused 2-week marketing sprint with clear deliverables.
What It Does
Structures your marketing work into time-boxed sprints with defined goals, task breakdowns, and success criteria. Prevents scope creep and ensures marketing ships, not just plans.
Time Investment
20-30 minutes (planning session)
Process
1. Review Context
Before planning, gather:
- What did last sprint accomplish? (If not first sprint)
- Current business priorities — what matters most right now?
- Any deadlines or external dependencies?
- Available capacity — how many hours/week for marketing?
2. Set Sprint Goal
One sentence: What is this sprint about?
Good examples:
- "Launch positioning and homepage copy for ProductX"
- "Build email nurture sequence for trial users"
- "Establish SEO content pipeline with 4 published posts"
- "Run competitive analysis and update positioning"
Bad examples:
- "Do marketing" (too vague)
- "Redesign everything" (too ambitious)
- "Post on social" (no outcome defined)
3. Define Deliverables
List 3-5 concrete deliverables that prove the sprint goal is met.
| # | Deliverable | Skill/Workflow | Est. Time | Owner |
|---|---|---|---|---|
| 1 | ... | ... | ... | ... |
| 2 | ... | ... | ... | ... |
| 3 | ... | ... | ... | ... |
Rules:
- Each deliverable must be a specific artifact (doc, page, campaign, etc.)
- Total estimated time must fit within available capacity
- If it doesn't fit → cut scope, don't extend timeline
4. Break Into Tasks
For each deliverable, list the tasks:
## Deliverable 1: [Name]
- [ ] Task 1 — [skill to use] — est. Xh
- [ ] Task 2 — est. Xh
- [ ] Task 3 — est. Xh
- [ ] Review & ship — est. 30m
5. Schedule the Sprint
Week 1: Research & Draft
- Day 1-2: Research tasks
- Day 3-4: First drafts
- Day 5: Review, feedback, iterate
Week 2: Polish & Ship
- Day 1-2: Revisions, finalize
- Day 3-4: Ship deliverables
- Day 5: Sprint retro →
/cm:retro
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 · 132 lines · 0 tokens per session scan A 8516b98228a1
cm-sprint 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 901 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-sprint compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cm-sprintclassicchins/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 |