Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/classicchins/compounding-marketingnpx agentmods add commands/classicchins/compounding-marketing/cm-uninstallWrote 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-uninstall)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/cm-uninstall"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-uninstall.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.01527 |
| Opus 5 | $0.00000 | $0.00763 |
| Sonnet 5 | $0.00000 | $0.00305 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade C, and why
cm-uninstall scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. **`rm -rf` on the install root** — always walk bottom-up and only remove empty dirs. How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cm-uninstall — Reverse a Compounding Marketing install
Reverse a previous /cm-setup or npx compounding-marketing install using the recorded manifest. Restores .bak backups byte-identical, strips marker blocks from CLAUDE.md / AGENTS.md, removes only files the wizard created.
What It Does
Loads .compounding-marketing-install.json and reverses every recorded change. Files the user authored remain untouched.
Manifest location:
- Global installs:
~/.claude/.compounding-marketing-install.json - Project / custom installs: project root (
./.compounding-marketing-install.json)
When To Use
- You installed via the wizard and want to remove every trace.
- You re-ran the wizard with a different scope/tool and want to undo the wrong one.
- You're cleaning up a CI/scratch environment.
What Gets Reversed
| Manifest field | Action |
|---|---|
appendedMarkers[] |
Open each instructions file, remove the block between <!-- COMPOUNDING-MARKETING-START --> and <!-- COMPOUNDING-MARKETING-END -->. All other content preserved verbatim. |
mcpEntries[] |
For each {file, format, serverName}: delete that server from .mcp.json (mcpServers.<name>) or config.toml ([mcp_servers.<name>]). Delete the file if it becomes empty. |
createdSymlinks[] |
Remove each symlink. The target file is never touched. |
createdFiles[] |
Delete each path (deepest first). |
modifiedFiles[].backupPath |
Restore the .bak to its original path. Delete the .bak. |
installRoot, commandsDir, skillsLinkDir, parent of mcpConfigFile |
Walked bottom-up; empty dirs removed (including tool-config wrappers .claude/, .cursor/, .codex/, .agents/). Non-empty dirs left alone. |
| Manifest file itself | Deleted last. |
Process
Step 1: Locate the manifest
Search in order:
~/.claude/.compounding-marketing-install.json(global)./.compounding-marketing-install.json(project, run from project root)./compounding-marketing/../.compounding-marketing-install.json(project, run from a sibling dir)
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 · 133 lines · 0 tokens per session scan C 84f27c6efc61
cm-uninstall is a command published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,527 tokens. A static security scan graded it C with 1 finding (recursive force delete). 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.