content-brief-generator

content-brief-generator is a skill for Claude Code from siddiqss/semantic-seo-suite. It costs 118 tokens per session (882 once invoked), scanned A, original, MIT.

A generator for detailed content briefs from a topic or search query, including an ordered page outline, related terms, links, and writing constraints.

In plain words
What is it for?
Use it to plan search-focused articles, define headings, choose internal links, set section lengths, target search-result snippets, and list facts that must not be invented.
Why use it?
It turns a broad topic into a structured plan that another writer can follow while reducing unsupported claims and missing page sections.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the semantic-seo-suite plugin — 10 skills shipped together

Good fit Use it to plan search-focused articles, define headings, choose internal links, set section lengths, target search-result snippets, and list facts that must not be invented.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/siddiqss/semantic-seo-suite/content-brief-generator
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 siddiqss/semantic-seo-suite --skill content-brief-generator
Clone the repo
git clone --depth 1 https://github.com/siddiqss/semantic-seo-suite

Made for: Claude Code.

Or install semantic-seo-suite, the plugin that ships this one along with the rest of its 10 skills.

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-brief-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/content-brief-generator/github.svg)](https://agentmods.dev/skills/siddiqss/semantic-seo-suite/content-brief-generator)
Your own site
<a href="https://agentmods.dev/skills/siddiqss/semantic-seo-suite/content-brief-generator"><img src="https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/content-brief-generator/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-brief-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/siddiqss/semantic-seo-suite/content-brief-generator"><img src="https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/content-brief-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 882 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.00118 $0.00882
Opus 5 $0.00059 $0.00441
Sonnet 5 $0.00024 $0.00176
Haiku 4.5 $0.00012 $0.00088

Measured 12d ago against content hash 864e7920c223, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

content-brief-generator 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 12d 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-brief-generator/SKILL.md · 73 lines

How it starts

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

content-brief-generator

Produce a brief a stranger writer could execute without further explanation, built on the page's contextual vector (heading order = meaning) and locked to one macro context.

Read first: ../../framework/contextual-vectors.md, ../../framework/macro-micro-semantics.md, ../../framework/query-semantics.md, ../../framework/internal-linking-rules.md.

Preconditions

  • brands/<slug>/config.yaml (tier).
  • A node in brands/<slug>/topical-map.json (or create an ad-hoc node from a query).

Workflow

  1. Load the node (target query, intent, entities, query network, internal links). If ad-hoc, first decompose the query's entity via ../../framework/eav-modeling.md.

  2. SERP recon for the target query:

    • T0: web_search + fetch the top 2–3 results; extract their heading structures and which entities/attributes they cover. Note gaps you can beat.
    • T2: ../../scripts/dataforseo_client.py live SERP + People-Also-Ask for cleaner data. Record provenance.
  3. Build the contextual vector (the outline). Order per contextual-vectors.md: definition/snippet lead → defining attributes → values/how-to → comparisons/related → question network → edge cases (macro-micro border with a grouper question). Tag each heading entity: / attr: / rel: / q:, state must_cover, set a word_budget guideline. Keep ONE macro context and one intent.

  4. Snippet target. Write the ~40-word extractive answer the lead should win.

  5. Internal links. Pull up/down/lateral from the node; add descriptive, varied anchor suggestions from the target nodes' query networks. Justify laterals (named shared attribute at T0; embedding distance at T1).

  6. Lock the facts. List locked_facts_refs (keys the article may state) and an explicit do_not_fabricate list (specs/stats/prices lacking provenance — pull the brand's _pending_owner_confirmation items into here).

  7. Intent-conflict check vs sibling nodes (query-semantics.md): flag any node with overlapping query network + same intent. T0 by judgement; T1 via ../../scripts/semantic_distance.py.

Read the full file on GitHub · 73 lines

Files

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.

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. 12d ago First seen · 73 lines · 118 tokens per session scan A 864e7920c223

Subscribe to this mod's changes

content-brief-generator is a skill published in the GitHub repository siddiqss/semantic-seo-suite (9 stars, last pushed 2mo ago), licensed MIT. It adds 118 tokens to every session and 882 once invoked, about $0.0006 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.