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-position)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/cm-position"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-position/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-position"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-position.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.00322 |
| Opus 5.5 | $0.00000 | $0.00129 |
| Sonnet 5.5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
cm-position 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:position — Full Positioning Workshop
Complete positioning workshop using April Dunford's framework + messaging development.
What It Does
Runs the full positioning stack: positioning → messaging → value props.
Process
-
Run Positioning Skill
- Execute
positioningskill - Output: Positioning canvas (alternatives, attributes, value, best-fit customers, category)
- Execute
-
Run Messaging Framework
- Execute
messaging-frameworkskill - Convert positioning into messaging pillars
- Output: Messaging framework with proof points
- Execute
-
Run Value Proposition (per segment)
- Execute
value-propositionskill for each customer segment - Output: Value proposition canvas per segment
- Execute
-
Synthesize into Positioning Package
- Combine all outputs
- Create single positioning document
- Save to
deliverables/positioning-package.md
-
Recommend Next Steps
- Update website copy → Run
/cm:copy - Plan launch → Run
/cm:launch - Create sales materials → Run
sales-enablementskill
- Update website copy → Run
When to Use
- Launching a new product
- Repositioning existing product
- Entering new market
- Confused messaging across channels
Prerequisites
- Run
/cm:researchfirst (or have existing product-market context)
Time Investment
3-5 hours
Output
- Positioning canvas
- Messaging framework
- Value proposition canvases (per segment)
- Unified positioning package document
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 · 55 lines · 0 tokens per session scan A 4a47bef532b8
cm-position 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 322 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-position compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cm-positionclassicchins/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 |