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 inhouseseo/superseo-skills --skill content-briefgit clone --depth 1 https://github.com/inhouseseo/superseo-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/inhouseseo/superseo-skills/content-brief)<a href="https://agentmods.dev/skills/inhouseseo/superseo-skills/content-brief"><img src="https://agentmods.dev/badge/skills/inhouseseo/superseo-skills/content-brief/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/inhouseseo/superseo-skills/content-brief"><img src="https://agentmods.dev/badge/skills/inhouseseo/superseo-skills/content-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 101 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00055 | $0.01464 |
| Opus 5 | $0.00028 | $0.00732 |
| Sonnet 5 | $0.00011 | $0.00293 |
| Haiku 4.5 | $0.00006 | $0.00146 |
Grade A, and why
content-brief 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Brief
A writer-ready content brief based on real SERP analysis. The agent Googles the target keyword, reads the top 10 results, classifies intent, identifies competitor gaps, and produces the brief. No keyword tool exports, no manual SERP pasting.
Input
Target keyword (required). Optionally: business context if you want the brief tailored to a specific audience/tone.
If the user didn't provide a keyword, ask for it before proceeding.
Role
You are a senior content strategist and SEO brief specialist with 10+ years of experience. Your job is to produce a complete, writer-ready brief based on what actually ranks right now — not a generic template.
Step 1: Research the SERP
Google the target keyword. Read the top 10 results. For each top-ranking page, note:
- Content format (listicle / long-form guide / comparison / how-to / tool / video)
- Approximate word count
- Heading structure (H1, main H2s)
- Content angle and unique hook
- What they cover that others don't
- Whether they appear to hold a featured snippet, People Also Ask positions, or other SERP features
Base every claim in the brief on pages you actually read. If a result won't fetch, say so and work from the ones you could read — don't infer what an unread page covers.
Step 2: Identify Search Intent
Classify dominant intent: Informational / Commercial Investigation / Transactional / Navigational.
Apply intent-specific length guidance:
- Informational: 1,500–3,000+ words — completeness, PAA coverage
- Commercial: 2,000–4,000 words — features, comparison, objectivity
- Transactional: 800–1,500 words — trust signals, CTAs, specs
- Navigational: 500–1,000 words — speed, direct info
Target word count = average of top 5 results + 10%. Never pad to hit a number.
Step 3: Map the People Also Ask
If PAA questions appear for this keyword, write them down verbatim. They'll become H2/H3 headings in the outline.
Step 4: Identify Content Type
Pick the content type from the SERP pattern. Content types: how-to, definition/explainer, comparison, listicle, product-review, case-study, pillar-page, faq-page, landing-page, service-page, category-page, buying-guide, alternatives-page, pricing-page, location-page.
What ships with it
6 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.
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.
- 8d ago Changed · +2 lines 9210a876af47
- 12d ago First seen · 115 lines · 55 tokens per session scan A be05dd3985cc
content-brief is a skill published in the GitHub repository inhouseseo/superseo-skills (320 stars, last pushed 8d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,464 once invoked, about $0.0003 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
scrapecreators-api
Scrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API. Covers TikTok, Instagram, YouTube, LinkedIn, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, TikTok Shop, Google, and link-in-bio services (Linktree, Komi, Pillar, Linkbio…
outlier-post-finder
Use when the user wants to find posts, videos, reels, shorts, tweets, or social content that overperformed versus a creator, brand, or competitor baseline. Finds outliers, explains why they worked, extracts hooks and formats, and produces a practical swipe file.
competitor-social-research
Use when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a practical social strategy brief from public social data.
ad-library-teardown
Use when the user wants to analyze active ads from Meta/Facebook, Google, or LinkedIn ad libraries; tear down a competitor's messaging; extract hooks, offers, CTAs, video transcripts, landing page claims, and test ideas from public ads.
comment-mining
Use when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos.
transcript-intelligence
Use when the user wants to summarize, analyze, or repurpose transcripts from TikTok, Instagram, YouTube, Facebook, X/Twitter, LinkedIn, Rumble, or Reddit video posts. Extracts hooks, claims, quotes, content atoms, themes, and reusable scripts.