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 instructions/classicchins/compounding-marketing/agents-mdgit 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/instructions/classicchins/compounding-marketing/agents-md)<a href="https://agentmods.dev/instructions/classicchins/compounding-marketing/agents-md"><img src="https://agentmods.dev/badge/instructions/classicchins/compounding-marketing/agents-md.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.01937 | $0.01937 |
| Opus 5 | $0.00968 | $0.00968 |
| Sonnet 5 | $0.00387 | $0.00387 |
| Haiku 4.5 | $0.00194 | $0.00194 |
Grade A, and why
compounding-marketing AGENTS.md 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compounding Marketing — Agent Instructions
Cross-platform marketing plugin (v1.6.0). 61 skills + 16 workflow commands covering positioning, messaging, copy, CRO, SEO, GTM, lifecycle, and growth. Works with Claude Code/Cowork, ChatGPT, Codex, Cursor, Zed, Windsurf, and any AI assistant that reads structured skill files. Philosophy: each unit of marketing work should make the next one easier.
Install (per tool)
| Tool | Command |
|---|---|
| Claude Code / Cowork | /plugin marketplace add classicchins/compounding-marketing then /plugin install compounding-marketing, then /cm-setup |
| Cursor | npx compounding-marketing --tool=cursor |
| Codex (OpenAI) | npx compounding-marketing --tool=codex --scope=global |
| ChatGPT (Custom GPT) | npx compounding-marketing --tool=chatgpt (prints paste-block + upload list) |
| Zed | npx compounding-marketing --tool=zed |
| Other | npx compounding-marketing --tool=other |
Flags: --dry-run, --yes, --uninstall, --scope=global|project|custom, --target=<path>. The wizard never modifies files without prompting (merge / overwrite-with-.bak / skip). See README.md for the full per-tool target table.
How skills work
Each skill is skills/<name>/SKILL.md with YAML frontmatter (name, description, metadata.version) and a validated 7-section body:
- Role prompt (40-80 lines) — persona, philosophy, authority
- Initial Assessment — prerequisites + 5-10 diagnostic questions
- Process — 5-10 numbered steps (how-to / decision criteria / gotchas)
- Output Format — fenced markdown template
- Quality Bar — checklist + ≥5 Common Mistakes (mistake / why / fix)
- Examples — ≥2 worked B2B SaaS scenarios
- Related Skills — ≥3 cross-references
When a user asks for marketing help, load the full SKILL.md and execute its Process step-by-step. Always check .agents/product-marketing-context.md first — it's the shared foundation created by cm-context and every other skill cross-references it.
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 · 101 lines · 1,937 tokens per session scan A 329256fe38a4
compounding-marketing AGENTS.md is an instructions file published in the GitHub repository classicchins/compounding-marketing (7 stars, last pushed 3mo ago), licensed MIT. It adds 1,937 tokens to every session, about $0.0097 per session on Opus 5. 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.