Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/robroyhobbs/marketing-skillsnpx agentmods add skills/robroyhobbs/marketing-skills/seo-contentWrote 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/robroyhobbs/marketing-skills/seo-content)<a href="https://agentmods.dev/skills/robroyhobbs/marketing-skills/seo-content"><img src="https://agentmods.dev/badge/skills/robroyhobbs/marketing-skills/seo-content/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/robroyhobbs/marketing-skills/seo-content"><img src="https://agentmods.dev/badge/skills/robroyhobbs/marketing-skills/seo-content.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.00211 | $0.13492 |
| Opus 5 | $0.00105 | $0.06746 |
| Sonnet 5 | $0.00042 | $0.02698 |
| Haiku 4.5 | $0.00021 | $0.01349 |
Grade A, and why
seo-content 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.
How it starts
The opening of the file, as written. The whole thing — 1,747 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/seo-content -- Publication-Ready SEO Content
SEO content has a reputation problem. Most of it is garbage -- keyword-stuffed, AI-sounding, says nothing new. It ranks for a month, then dies.
This skill creates content that ranks AND builds trust. Content that sounds like an expert sharing what they know, not a content mill churning out filler.
The goal: Would someone bookmark this? Would they share it? Would they come back?
If yes, Google will reward it. If no, no amount of optimization saves it.
Read ./brand/ per _system/brand-memory.md
Follow all output formatting rules from _system/output-format.md
Brand Memory Integration
On every invocation, check for existing brand context.
Reads (if they exist)
| File | What it provides | How it shapes output |
|---|---|---|
| ./brand/voice-profile.md | Tone, personality, vocabulary, rhythm | Directly shapes the writing style -- a "direct, proof-heavy" voice writes differently than a "warm, story-driven" voice |
| ./brand/keyword-plan.md | Prioritized keywords, content briefs, SERP data | Provides target keyword, cluster, intent, content type, and any pre-gathered SERP analysis |
| ./brand/audience.md | Buyer profiles, sophistication level, pain points | Informs how technical to write, what examples to use, what pain points to address |
| ./brand/positioning.md | Market angles, differentiators | Shapes the unique angle for the piece -- how your perspective differs from everyone else ranking |
| ./brand/competitors.md | Named competitors, their positioning | Identifies what angle competitors take so you can differentiate |
| ./brand/learnings.md | Past performance data | Reveals what content approaches worked before -- long-form vs short, story-driven vs data-driven |
Writes
| File | What it contains |
|---|---|
| ./campaigns/content/{keyword-slug}.md | The publication-ready article with frontmatter |
| ./brand/assets.md | Appends entry for the created content piece |
| ./brand/learnings.md | Appends findings after feedback collection |
What ships with it
1 file 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.
- 11d ago First seen · 1,747 lines · 211 tokens per session scan A dad3db43bb99
seo-content is a skill published in the GitHub repository robroyhobbs/marketing-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 211 tokens to every session and 13,492 once invoked, about $0.0011 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-31.
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…