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/workflow-commandsgit 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/workflow-commands)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/workflow-commands"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/workflow-commands.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 | $0.00000 | $0.03181 |
| Opus 5 | $0.00000 | $0.01590 |
| Sonnet 5 | $0.00000 | $0.00636 |
| Haiku 4.5 | $0.00000 | $0.00318 |
Grade A, and why
workflow-commands 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 4d 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 — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Commands Reference
Complete reference for all workflow commands with examples.
/cm:daily — Daily Marketing Review
Purpose: 10-minute daily check-in on marketing state
Time: 10-15 minutes
When to use: Start of each workday, during launch week
What it does:
- Asks what campaigns/content are live
- Checks performance snapshot (traffic, signups, key metrics)
- Identifies wins and red flags
- Defines today's ONE marketing priority
Example Output:
# Daily Marketing Review — Mar 14, 2026
## What's Live
- **Campaigns:** LinkedIn retargeting (Week 2), Google Search (paused for creative refresh)
- **Content:** Pricing blog post published yesterday (ranking #4 for "SaaS pricing")
- **Sequences:** Trial activation sequence (423 active users)
## Performance Snapshot
- **Traffic:** 2,847 (+12% vs last week)
- **Signups:** 34 (+6 vs yesterday)
- **Trial→Paid:** 18% (stable)
## Wins 🏆
- Pricing blog hit #4 in 3 days (outcome-focused headline worked)
## Flags ⚠️
- LinkedIn CPC up 23% — creative fatigue, need refresh
## Today's Focus
1. **Priority:** Finish homepage copy rewrite (due to design by 3pm)
2. **Quick wins:** Schedule 3 social posts, reply to PR inquiry from TechCrunch
Files created: None (mental model update only)
/cm:standup — Marketing Standup
Purpose: 5-minute standup (what shipped, what's next, blockers)
Time: 5 minutes
When to use: Daily or every other day
Example Output:
# Marketing Standup — Mar 14, 2026
## Yesterday ✅
- Published pricing blog post
- Set up LinkedIn retargeting campaign
- Continued homepage copy revision (80% done)
## Today 🎯
- Finish homepage copy → ready for design by 3pm
- Draft cold email sequence for enterprise (first 2 emails)
- Review competitor's new landing page
## Blockers ⚠️
- Waiting on customer quote approval from Sarah @ Acme
- Need product screenshots for homepage (asked design yesterday)
/cm:eod — End of Day Wrap
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.
- 4d ago First seen · 453 lines · 0 tokens per session scan A bba18debe1a4
workflow-commands 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 3,181 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
git
Git operations with intelligent commit messages and workflow optimization.
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.