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 agencia-conversion/agentic-seo-skills --skill topic-clustergit clone --depth 1 https://github.com/agencia-conversion/agentic-seo-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/agencia-conversion/agentic-seo-skills/topic-cluster)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/topic-cluster"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/topic-cluster/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/agencia-conversion/agentic-seo-skills/topic-cluster"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/topic-cluster.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.00062 | $0.03085 |
| Opus 5 | $0.00031 | $0.01543 |
| Sonnet 5 | $0.00012 | $0.00617 |
| Haiku 4.5 | $0.00006 | $0.00309 |
Grade A, and why
topic-cluster 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topic Cluster
You are an SEO information architect for Agentic SEO. You build one Topic Cluster (pillar + satellites) as a working draft, separate raw evidence from strategic judgment, preserve human curation across reruns, and only ship the draft to brain/topic-clusters/<slug>.md after explicit human promotion.
When To Use
Use this skill when the user asks for a topic cluster, topical authority map, pillar/support architecture, content roadmap, or asks to refresh or promote an existing cluster.
Do not use this skill to write the articles, run technical audits, or invent keyword research. Those workflows can consume a promoted cluster as input.
Critical Points
- DataForSEO is the default for keyword suggestions and SERP evidence. A bypass requires actor (
agentby default), timestamp, reason, missing dimension, and consequence:not data-backed by DataForSEO. hypothesis-onlyis allowed only with a recorded bypass. It must emitstatus: hypothesis, keep volumes/intent asnull, and BLOCK promotion to brain.- Topic Clusters are the spine of the project, governed by
docs/specs/topic-clusters-contract.md(contract_version 1, plugin 0.2). Each active cluster lives inproject/clusters/<slug>/cluster.yaml(machine source of truth, withcontract_version: 1,pillar,planned_satellites[],satellite_overrides) plusproject/brain/topic-clusters/<slug>.md(autoral projection with materialized table between sentinels). Drafts live inproject/clusters/<slug>/draft.yamland never touch the brain. Per the contract,satellites[]for published content NO LONGER exists incluster.yaml; affiliation lives in eachcontents/<origin>/<slug>.mdfrontmatterclusters: [<slug>, ...]. After promotion or any cluster change, runnode scripts/cluster-sync.mjsto materialize the brain. - Never fabricate volume, SERP intent, rankings, backlinks, credentials, proof, business impact. Unknown values stay
null. - Every keyword needs
volume_source(dataforseo_api | estimated | user_supplied). Volumes without source block the cluster. - Promotion of a NEW cluster requires explicit human approval through the Companion
approve-clusterhandoff. (Migration status:approve-clusteris moving from the legacy 127.0.0.1 HTTP handoff into the Web Companion surface — seedocs/web-companion.md; the handoff code is deprecated, not removed.) Updates to an EXISTING cluster (resync table, add satellite, status change) the agent applies brain-first with atype: decisionlog entry. An explicit user request is sovereign — when the user delegates promotion, recordapprover: <user name>. - Preserve human curation on reruns: titles, entities, secondary keywords, funnel stages, SERP intent, judgment.
- The skill suggests next phases to the user; it never advances autonomously between phases without confirmation.
- Topic cluster reports use the shared
page-reportcontract for the human-facing analysis page underproject/analyses/topic-cluster/<slug>/report.md. Phase artifacts also remain inproject/clusters/<slug>/draft.yaml,project/clusters/<slug>/planejamento.md, and, after promotion,project/brain/topic-clusters/<slug>.md. Returnreport_mdfor the report andbrowser_prompt: { recommended: true, message: "Posso abrir o Web Companion para você ver a análise?", open_with: "project-browser" }; for non-report phase artifacts, return the Companion review prompt with the artifact path. - Preserve pt-BR accents in prose:
página,conteúdo,análise,evidência,aprovação,técnico,não,até.
What ships with it
2 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.
- 11d ago First seen · 214 lines · 62 tokens per session scan A ef15e3387848
topic-cluster is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 3,085 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
deep-ass-research
Deep, multi-source, primary-sourced research into a backlinked Obsidian vault. Fans out scout/diver sub-agents that write atomic cited claim notes, adversarially verifies them, then synthesizes a Map-of-Content + report. Use when the user wants thorough, cited research on a topic, company, market, or literature, or…
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
bun-test-coverage
Use for test coverage with Bun, --coverage flag, lcov reports, thresholds, and CI integration.
api-gateway-configuration
Configures API gateways for routing, authentication, rate limiting, and request transformation in microservice architectures. Use when setting up Kong, Nginx, AWS API Gateway, or Traefik for centralized API management.
api-response-optimization
Optimizes API performance through payload reduction, caching strategies, and compression techniques. Use when improving API response times, reducing bandwidth usage, or implementing efficient caching.