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 manojbajaj95/claude-gtm-plugin --skill content-strategy-and-planninggit clone --depth 1 https://github.com/manojbajaj95/claude-gtm-pluginWrote 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/manojbajaj95/claude-gtm-plugin/content-strategy-and-planning)<a href="https://agentmods.dev/skills/manojbajaj95/claude-gtm-plugin/content-strategy-and-planning"><img src="https://agentmods.dev/badge/skills/manojbajaj95/claude-gtm-plugin/content-strategy-and-planning/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/manojbajaj95/claude-gtm-plugin/content-strategy-and-planning"><img src="https://agentmods.dev/badge/skills/manojbajaj95/claude-gtm-plugin/content-strategy-and-planning.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.00177 | $0.03501 |
| Opus 5 | $0.00088 | $0.01750 |
| Sonnet 5 | $0.00035 | $0.00700 |
| Haiku 4.5 | $0.00018 | $0.00350 |
Grade A, and why
content-strategy-and-planning 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 12d 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategy & Planning
Workspace Context
Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.
Operating Contract
This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.
Unified skill combining strategic content planning, positioning, and operational execution frameworks.
When to Use
- Planning what content to create and why
- Developing content pillars and topic clusters
- Building editorial calendars
- Creating messaging hierarchy and positioning
- Trust-building content strategy
- Measuring content ROI
- GEO (AI search) optimization planning
Part 1: Strategic Planning
Step 1: Define Business Context
Before planning, gather:
| Input | Why It Matters |
|---|---|
| Product/service description | Maps content to value proposition |
| Ideal customer profile (ICP) | Determines language, channels, pain points |
| Primary goal | Traffic, leads, brand awareness, thought leadership |
| Current content inventory | What's working vs. gaps |
| Resources available | Writers, budget, time constraints |
Step 2: Searchable vs Shareable Framework
Every piece of content must be searchable, shareable, or both. Prioritize in that order.
Searchable content captures existing demand:
- Target specific keywords/questions
- Match search intent exactly
- Use clear titles matching queries
- Optimize for AI/LLM discovery
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 419 lines · 177 tokens per session scan A ea6e0b6d5a35
content-strategy-and-planning is a skill published in the GitHub repository manojbajaj95/claude-gtm-plugin (100 stars, last pushed 3mo ago), licensed MIT. It adds 177 tokens to every session and 3,501 once invoked, about $0.0009 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-30.
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…