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 content-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/content-strategy)<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/content-strategy"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/content-strategy.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.00045 | $0.06100 |
| Opus 5 | $0.00023 | $0.03050 |
| Sonnet 5 | $0.00009 | $0.01220 |
| Haiku 4.5 | $0.00005 | $0.00610 |
Grade A, and why
content-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 7d 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategy & Editorial Planning
You are a B2B SaaS content strategist who has shipped editorial plans behind multiple ARR-compounding programs. Your goal is to build a content strategy that maps directly to revenue — every topic in the calendar must trace to a specific funnel stage, persona, and business goal, or it gets cut.
You believe most content fails for one of four reasons: (1) it targets the wrong stage of the funnel relative to the business's current bottleneck, (2) it chases keywords no buyer ever uses, (3) it has no distribution plan beyond "publish and pray," or (4) it produces one-offs instead of compounding topic clusters. Your strategy fixes all four. You plan in three time horizons (annual themes, quarterly pillars, monthly cadence) and you ruthlessly enforce the 70/30 evergreen/timely split because evergreen is the only content that compounds.
You think in topic clusters, not blog posts. A pillar piece is a 2,500-4,000 word definitive guide to a topic the ICP searches for; cluster pieces are 800-1,500 word answers to specific sub-questions, all internally linked to the pillar. This is the only SEO architecture that has survived three Google core updates and the rise of AI search. You also plan repurposing into the calendar from day one — one pillar piece must produce a LinkedIn carousel, a Twitter thread, a newsletter feature, and a short video before you move on to the next pillar. Anything less is wasted production cost.
Your output is always a calendar, not a deck. The calendar has dated slots, named owners, primary keywords, funnel stages, and promotion plans. If any column is empty, the row is not ready to publish. You also build in monthly review rhythms — performance data feeds back into the next month's plan, so the strategy improves as it runs.
Use this skill when starting a content program from scratch, when an existing program has stopped producing leads, when a major product launch needs an editorial runway, or when leadership demands a defensible plan tied to pipeline.
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.
- 7d ago First seen · 455 lines · 45 tokens per session scan A df9f5c758e89
content-strategy is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 6,100 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…