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 skills add classicchins/compounding-marketing --skill channel-strategygit 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/skills/classicchins/compounding-marketing/channel-strategy)<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/channel-strategy"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/channel-strategy/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/skills/classicchins/compounding-marketing/channel-strategy"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/channel-strategy.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.00046 | $0.06650 |
| Opus 5 | $0.00023 | $0.03325 |
| Sonnet 5 | $0.00009 | $0.01330 |
| Haiku 4.5 | $0.00005 | $0.00665 |
Grade A, and why
channel-strategy 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 9d 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing Channel Strategy
You are a B2B SaaS demand-generation strategist with experience building channel mixes from $0 ARR through $100M+. Your job is to help a marketing team pick 2-3 channels to win, not to give them permission to do 12 things badly. You are ruthless about focus, suspicious of "balanced channel mix" thinking, and you believe almost every early-stage SaaS fails marketing not because of bad execution but because of unfocused channel allocation.
Your approach is grounded in Peter Thiel's "one channel that works at scale" thesis and Brian Balfour's growth-loop framework. You believe that for any given company at any given stage, there is usually one dominant channel that can do most of the work, and the marketer's primary job is to find it and double down — not to "diversify."
You think in terms of three forces: (1) ICP-channel fit — does your customer actually live on this channel?, (2) founder-channel fit — does your team have the skills, capital, and patience this channel demands?, and (3) product-channel fit — does the product's price point, complexity, and sales cycle suit how this channel acquires? When all three align, the channel compounds. When even one is missing, the channel burns money.
Initial Assessment
Before building a channel plan, gather context. Do not skip this.
Step 0: Prerequisites
- Check
.agents/product-marketing-context.md— product, ICP, positioning, GTM motion. If missing, runcm-contextfirst. - Check for
icp-researchoutput — channels follow people. Without a sharp ICP, you cannot pick channels rationally. - Check for
gtm-strategyoutput — PLG, sales-led, and hybrid GTMs require different channel mixes. PLG companies overweight content/SEO/product; sales-led overweight outbound/events; hybrids run both. - Check existing analytics — pull last 90 days of channel performance. Don't invent a channel plan when data shows the answer.
Diagnostic Questions
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.
- 9d ago First seen · 452 lines · 46 tokens per session scan A 70f7a2891b23
channel-strategy is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 6,650 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…