content-strategy

content-strategy is a skill for Claude Code, Codex from vstorm-co/content-skills. It costs 43 tokens per session (1,754 once invoked), scanned A, original, MIT.

A planning guide for deciding who content is for, what it should communicate, and which recurring themes should shape publishing.

In plain words
What is it for?
Use it to plan content strategy, generate ideas, define content pillars, create briefs, and set editorial positioning that other content tools can carry out.
Why use it?
It helps turn broad marketing or editorial goals into a clear position and usable content direction before individual pieces are written.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan content strategy, generate ideas, define content pillars, create briefs, and set editorial positioning that other content tools can carry out.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vstorm-co/content-skills/content-strategy
Install

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.

Any agent
npx skills add vstorm-co/content-skills --skill content-strategy
Clone the repo
git clone --depth 1 https://github.com/vstorm-co/content-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for content-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-strategy/github.svg)](https://agentmods.dev/skills/vstorm-co/content-skills/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/vstorm-co/content-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-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.

agentmods 80×15 button for content-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/vstorm-co/content-skills/content-strategy"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,754 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01754
Opus 5 $0.00022 $0.00877
Sonnet 5 $0.00009 $0.00351
Haiku 4.5 $0.00004 $0.00175

Measured 10d ago against content hash 338df23b60b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 10d 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.

skills/content-strategy/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Content Strategy & Ideation

Before You Start

  1. Check for existing brand context: Read brand/VOICE.md and brand/VISUAL.md if they exist. Strategy work must align with the established brand identity. If no brand files exist, the strategy phase is a good time to define them -- suggest the user run content-setup first, or build foundational voice/visual decisions into the strategy output.

  2. Understand the distinction between strategy and tactics:

    • Strategy answers: Who are we talking to? What do we want them to think/feel/do? What is our unique position? What themes define our content?
    • Tactics answer: What specific pieces do we publish? When? Where? In what format?
    • This skill handles strategy first, then translates it into tactical briefs that other skills (content-blog, content-twitter, content-video, etc.) can execute.
  3. Gather context: Before strategizing, you need to understand the user's situation. Use the questions in questions.md as a starting framework. Not every question applies to every situation -- use judgment about which to ask and which to infer.


Ideation Flow

Follow these four stages in order. Each stage builds on the previous one.

Stage 1: Audience Analysis

Define who the content is for. Use the audience persona framework from frameworks/audience-persona.md.

For each target audience segment, document:

  • Demographics: Role, seniority, company size, industry
  • Psychographics: Values, beliefs, worldview, identity markers
  • Information diet: Where do they currently get information? Who do they follow? What formats do they prefer?
  • Pain points: What problems keep them up at night? What frustrates them about existing solutions or content?
  • Aspirations: What do they want to become or achieve? What does success look like for them?
  • Current beliefs: What do they already believe about your topic? What misconceptions exist?
  • Desired beliefs: What should they believe after consuming your content?

Read the full file on GitHub · 178 lines

Files

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.

Changes

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.

  1. 10d ago First seen · 178 lines · 43 tokens per session scan A 338df23b60b9

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository vstorm-co/content-skills (22 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,754 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.