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 siddiqss/semantic-seo-suite --skill content-brief-generatorgit clone --depth 1 https://github.com/siddiqss/semantic-seo-suiteWrote 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/siddiqss/semantic-seo-suite/content-brief-generator)<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.
<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>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.00118 | $0.00882 |
| Opus 5 | $0.00059 | $0.00441 |
| Sonnet 5 | $0.00024 | $0.00176 |
| Haiku 4.5 | $0.00012 | $0.00088 |
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.
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
-
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. -
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.pylive SERP + People-Also-Ask for cleaner data. Record provenance.
- T0:
-
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:, statemust_cover, set aword_budgetguideline. Keep ONE macro context and one intent. -
Snippet target. Write the ~40-word extractive answer the lead should win.
-
Internal links. Pull
up/down/lateralfrom the node; add descriptive, varied anchor suggestions from the target nodes' query networks. Justify laterals (named shared attribute at T0; embedding distance at T1). -
Lock the facts. List
locked_facts_refs(keys the article may state) and an explicitdo_not_fabricatelist (specs/stats/prices lacking provenance — pull the brand's_pending_owner_confirmationitems into here). -
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.
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.
- 12d ago First seen · 73 lines · 118 tokens per session scan A 864e7920c223
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.
Other skills, from other repositories
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
content-scoring
Score content against the 10 GEO criteria with evidence and prioritized fixes. Use when users ask to score, rate, evaluate, or estimate ranking strength.
schema-generator
Generate JSON-LD schema markup for pages and content types with an implementation checklist. Use when users ask for schema, structured data, rich snippets, or markup.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
validation-doctor
Check Brave Search and Chrome DevTools MCP availability and provide exact setup snippets. Use when validation dependencies are missing or uncertain.