What is topical-map-builder?

A content-structure builder that turns a brand foundation into linked main topics, related groups, and supporting pages, separated into central and neighbouring subjects.

Creating content plans, grouping search queries by topic and intent, and deciding which pages support the brand's main commercial subjects.

It provides a complete, organised view of what a site could cover instead of an unstructured list of keywords.

topical-map-builder — Skill for Claude Code by siddiqss

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 topical-map-builder

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/topical-map-builder/github.svg)](https://agentmods.dev/skills/siddiqss/semantic-seo-suite/topical-map-builder)

Your own site

<a href="https://agentmods.dev/skills/siddiqss/semantic-seo-suite/topical-map-builder"><img src="https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/topical-map-builder/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/siddiqss/semantic-seo-suite/topical-map-builder"><img src="https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/topical-map-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 132 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,113 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.

Model	Per session	Once invoked
Fable 5.1	$0.00132	$0.01113
Opus 5	$0.00066	$0.00557
Sonnet 5	$0.00026	$0.00223
Haiku 4.5	$0.00013	$0.00111

Measured 10d ago against content hash 165d47712315, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

topical-map-builder 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 10d 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/topical-map-builder/SKILL.md · 87 lines

How it starts

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

topical-map-builder

Turn a brand's foundation into an executable content architecture: a processed topical map of pillars → clusters → supporting pages, each with an intent and a query network, split into core (monetizing) and outer (authority-feeding) sections.

Read these first: ../../framework/topical-map-theory.md, ../../framework/eav-modeling.md, ../../framework/query-semantics.md. (And 00-overview.md for provenance rules if not already this session.)

Preconditions

Read brands/<slug>/config.yaml (tier).
Require brands/<slug>/entity-profile.json. If absent, run seo-brand-foundation first — do not build a map without a foundation.

Workflow

Decompose the central entity (raw map). Using the entity profile's attribute inventory + eav-modeling.md, over-generate: every attribute → candidate topics; values/comparisons/how-tos → sub-topics; questions/edge-cases → supporting topics; neighbouring entities → outer topics. Completeness first; don't filter yet.
Apply the core/outer split from the entity profile's boundary rule. Tag each candidate core or outer. Drop anything failing the "right to cover" test (source-context.md) — respect the will-not-cover list.
Expand query networks per node (query-semantics.md), at the configured tier:
- T0: reason out the network + validate a few via web_search; intent asserted.
- T1: ../../scripts/fetch_autocomplete.py (real variants, measured), optional ../../scripts/fetch_trends.py (relative demand), and ../../scripts/serp_intent_classifier.py to upgrade intent to measured.
- T2: ../../scripts/dataforseo_client.py for volume/difficulty/PAA (measured). Never invent search volumes.
Process the map: assign tier (pillar/cluster/supporting), parent, and one intent per node. Merge near-duplicates:
- T1+: ../../scripts/cluster_keywords.py on query networks → flag & merge sibling pairs above cannibalization_threshold.
- T0: merge by judgement (one URL, one intent).

Read the full file on GitHub · 87 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.

evals/evals.json 1.2 KB

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.

10d ago First seen · 87 lines · 132 tokens per session scan A 165d47712315

Subscribe to this mod's changes

topical-map-builder is a skill published in the GitHub repository siddiqss/semantic-seo-suite (9 stars, last pushed 2mo ago), licensed MIT. It adds 132 tokens to every session and 1,113 once invoked, about $0.0007 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.

Claude Code Marketing and SEO aeo claude-skills content-marketing generative-engine-optimization geo

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.

leopard627/fire-your-seo-agency · 162 tokens

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.

mverab/eGEOagents · 62 tokens

topical-map-builder

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

topical-map-builder

Preconditions

Workflow

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

fire-your-seo-agency

geo-loop

content-scoring

competitive-analysis

schema-generator

validation-doctor