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 agentmods add skills/drvoss/everything-copilot-cli/content-strategynpx skills add drvoss/everything-copilot-cli --skill content-strategygit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWhat 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 | $0.00037 | $0.02012 |
| Opus 5 | $0.00018 | $0.01006 |
| Sonnet 5 | $0.00007 | $0.00402 |
| Haiku 4.5 | $0.00004 | $0.00201 |
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 2d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategy
Content strategy is the intersection of what your audience searches for, what you have authority to say, and what supports your business goals. This skill helps you build a data-driven content plan — not a random blog schedule.
Core Framework
Business Goal → Target Audience → Keyword Research → Topic Clusters → Content Calendar
Step 1: Define Your Content Goals
> Help me define a content strategy for [product/company]:
>
> Product: [what you sell]
> Target customer: [who they are, what they care about]
> Business goal: [increase signups / build authority / retain users / etc.]
> Current content state: [have nothing / have a blog / have docs but no marketing content]
>
> What type of content strategy would best serve these goals?
Content strategy types:
- SEO-led: Target high-volume keywords; build organic traffic at scale
- Authority-led: Publish original research, opinions, and deep expertise
- Product-led: Content that drives product usage (tutorials, use cases)
- Community-led: User-generated content, forums, templates
Step 2: Keyword Research
Seed Keywords
> I'm building a content strategy for [product/niche].
>
> Generate 20 seed keywords organized by intent:
> - Informational (how-to, what-is, learn)
> - Commercial (best, vs, review, alternatives)
> - Transactional (buy, sign up, free trial)
>
> For each keyword, estimate: search volume (rough order: hundreds / thousands / 10k+),
> competition level (low / medium / high), and funnel stage (awareness / consideration / decision)
Long-tail Expansion
> For the seed keyword "[main keyword]":
> Generate 15 long-tail variations that:
> - Have lower competition
> - Address specific use cases
> - Include question-format keywords (who, what, how, why, when)
>
> These should represent real queries your target users would type.
Content Gap Analysis
> Our top competitors in this space are: [Competitor A, B, C]
>
> Based on what I know about their content strategies, what topic areas
> are likely underserved that we could own?
>
> Prioritize by: search demand, our credibility to publish on this topic,
> and strategic differentiation value.
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.
- 2d ago First seen · 227 lines · 37 tokens per session scan A 0195340cc0fe
content-strategy is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 2,012 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
flywheel-sync
Meta-skill that audits health of the entire product launch engine, identifies broken links between phases, and generates improvement roadmaps. Use when: system health, skill audit, launch engine health, are our skills working together, process audit, workflow health check.
growth-loop
Retention, expansion, and advocacy strategy that maximizes customer lifetime value through structured lifecycle programs. Use when: retention strategy, customer retention, expansion strategy, churn prevention, customer success, NRR, upsell, advocacy program.
launch-debrief
Structured post-launch retrospective that produces quantified learnings and improvement playbooks. Use when: launch retrospective, post-launch review, what worked, launch debrief, post-mortem, lessons learned.
budget-allocator
Launch budget optimization using portfolio theory and scenario analysis with experimentation reserves. Use when: budget allocation, marketing budget, launch budget, how much to spend, budget planning, channel budget.
gtm-exec-plan
Creates a polished 3-4 page GTM executive brief and plan with a 4-slide PowerPoint deck. Orchestrates market analysis, positioning, competitive intel, channel strategy, and launch planning into exec-ready deliverables. Use when: GTM plan, go-to-market plan, GTM strategy, GTM brief, executive GTM plan, GTM deck, GTM…
launch-pulse
GTM analytics and measurement framework that builds metrics architecture, dashboard specs, and alert systems. Use when: GTM metrics, launch metrics, measurement framework, KPIs, dashboard design, what should we measure, analytics framework.