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 ariadoss/superskills --skill content-strategygit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/content-strategy)<a href="https://agentmods.dev/skills/ariadoss/superskills/content-strategy"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/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/ariadoss/superskills/content-strategy"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/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.00095 | $0.01622 |
| Opus 5 | $0.00048 | $0.00811 |
| Sonnet 5 | $0.00019 | $0.00324 |
| Haiku 4.5 | $0.00010 | $0.00162 |
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 6d 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.
This is a copy
100% identical to content-strategy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Content: Content Strategy
Guides content strategy for SEO: topic clusters, pillar pages, cluster articles, and editorial planning. For content marketing across all channels (blog, email, social, video), see content-marketing. For translation workflow and multilingual content, see translation.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and proof points.
Identify:
- Keywords: From keyword research — see keyword-research for discovery and clustering
- Existing content: What already exists
- Resources: Content capacity, tools
- Goals: Traffic, conversions, authority
Product-Led SEO: Do SEO around product/users, not around industry/search engines. See seo-strategy for Product-Led SEO principle, products suited for SEO, and workflow order.
Topic Clusters
Topic clusters organize content by topic rather than isolated keywords. A pillar page covers a broad core topic; cluster articles cover subtopics; all connect via internal links. This signals topical authority to search engines and AI systems.
Structure
Pillar page (broad topic, 2,000-5,000+ words)
<-> internal links
Cluster 1 (subtopic, 800-2,500 words)
Cluster 2 (subtopic)
...
Cluster 6-12 (subtopics)
<-> cluster to cluster links
Pillar Page
| Attribute | Guideline |
|---|---|
| Length | 2,000-5,000+ words; comprehensive guide |
| Keyword | Broad head term with search volume |
| Role | Hub; links to all cluster articles; targets primary topic |
| Conversion | Link to product/feature pages where relevant |
Cluster Articles
| Attribute | Guideline |
|---|---|
| Count | 6-12 articles per pillar (minimum 6 for authority) |
| Length | 800-2,500 words each; focused on one subtopic |
| Keyword | Long-tail, specific intent per article |
| Links | Each cluster links to pillar; pillar links back; related clusters link to each other |
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.
- 6d ago First seen · 141 lines · 95 tokens per session scan A f9b4ecf686e9
content-strategy is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 4d ago), licensed MIT. It adds 95 tokens to every session and 1,622 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to content-strategy, differing in 0 lines, and is treated as a copy.
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…