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 shawnpang/startup-founder-skills --skill content-strategygit clone --depth 1 https://github.com/shawnpang/startup-founder-skillsWrote 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/shawnpang/startup-founder-skills/content-strategy)<a href="https://agentmods.dev/skills/shawnpang/startup-founder-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/content-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/shawnpang/startup-founder-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/content-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.00041 | $0.01728 |
| Opus 5 | $0.00020 | $0.00864 |
| Sonnet 5 | $0.00008 | $0.00346 |
| Haiku 4.5 | $0.00004 | $0.00173 |
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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- content-strategy — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategy
When to Use
- Building a content program from scratch for a startup.
- Deciding what content types to invest in first.
- Identifying content pillars and topic clusters.
- Planning an editorial calendar for the next 30/60/90 days.
- Evaluating whether existing content is working and what gaps exist.
- Choosing between searchable (SEO) and shareable (social) content investments.
Context Required
- From startup-context: product description, ICP, value proposition, competitive positioning, stage, existing traction, team capacity.
- From the user: current content assets (if any), distribution channels in use, business goals for content (traffic, leads, brand awareness, thought leadership), team capacity (who writes, how often), target topics or keywords of interest, customer research available (sales calls, surveys, support tickets).
Workflow
- Gather context before planning -- Assess four dimensions: (a) business context -- what the company does, who it serves, what problems it solves; (b) customer research -- pre-purchase questions, sales objections, support patterns, customer vocabulary; (c) current state -- existing content performance, available resources, production capabilities; (d) competitive landscape -- what competitors publish, market content gaps.
- Classify the content need -- Is the goal searchable content (SEO-driven, captures existing demand) or shareable content (social-native, creates demand)? Most startups need both but should weight based on stage:
- Pre-PMF: lean toward shareable (faster feedback, builds audience)
- Post-PMF: lean toward searchable (compounds over time, captures demand)
- Identify 3-5 content pillars -- Each pillar is a core topic your brand owns, spawning related content clusters. Use four identification methods:
- Product-led: Problems your product solves
- Audience-led: What your ICP needs to learn
- Search-led: Topic volume in your space
- Competitor-led: What competitors rank for (and gaps they miss)
- Pillar criteria: aligns with product, matches audience interests, has search volume or social interest, broad enough for multiple subtopics.
- Map content types to pillars -- Select from proven content formats:
- Use-case content: "[Persona] + [use-case]" targeting long-tail keywords -- bottom of funnel, high intent
- Hub-and-spoke: Comprehensive pillar page with linked subtopic articles -- SEO authority play
- Templates and tools: Downloadable resources that solve a micro-problem -- lead generation
- Thought leadership: Contrarian takes, original data, founder stories -- brand and trust
- Case studies: Customer transformation stories (Challenge, Solution, Results, Learnings) -- proof
- Comparison pages: "[Product] vs [Competitor]" -- captures switching intent
- Data-driven content: Product data analysis (anonymized), public data analysis, original research
- Expert roundups: 15-30 experts answering one specific question -- built-in distribution
- Score and prioritize -- Rate each content idea on four weighted dimensions:
- Customer impact (40%): Frequency in research, percentage of customers affected, emotional charge
- Content-market fit (30%): Problem-solution alignment, unique insights available, natural path to product
- Search potential (20%): Monthly volume, competition level, long-tail opportunities, growth trajectory
- Resource requirements (10%): Internal expertise, research needs, required assets
- Map to buyer journey -- Ensure coverage across awareness stages using keyword modifiers:
- Awareness: "what is," "how to," "guide to" -- thought leadership, educational content
- Consideration: "best," "top," "vs," "alternatives" -- comparison pages, how-to guides
- Decision: "pricing," "reviews," "demo," "trial" -- case studies, use-case content
- Implementation: "templates," "examples," "tutorial," "setup" -- onboarding content, feature deep-dives
- Build the editorial calendar -- Assign content to a realistic publishing cadence. For early-stage: 1-2 high-quality pieces per week beats daily low-effort posts.
- Define distribution plan -- Every piece needs a distribution path. Budget 50% of effort for distribution. A great article with no distribution plan underperforms a good article with a strong distribution plan.
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.
- 11d ago First seen · 87 lines · 41 tokens per session scan A d654646b3efc
content-strategy is a skill published in the GitHub repository shawnpang/startup-founder-skills (321 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,728 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-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…