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 Infrasity-Labs/dev-gtm-claude-skills --skill blog-clustergit clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-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/infrasity-labs/dev-gtm-claude-skills/blog-cluster)<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/blog-cluster"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-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/infrasity-labs/dev-gtm-claude-skills/blog-cluster"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-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.00135 | $0.04103 |
| Opus 5 | $0.00068 | $0.02051 |
| Sonnet 5 | $0.00027 | $0.00821 |
| Haiku 4.5 | $0.00014 | $0.00410 |
Grade A, and why
blog-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 9d 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.
This is a copy
89% identical to blog-cluster — 43 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Cluster (Semantic Topic Cluster Engine)
Plans and executes entire interlinked content ecosystems from a single seed keyword. Three layers: Semantic Clustering (the brain), Cluster Architecture (the structure), and Execution Engine (the machine).
Commands
| Command | What it does |
|---|---|
/blog cluster |
Interactive. Asks whether to plan or execute. |
/blog cluster plan <seed-keyword> |
SERP-based semantic analysis. Outputs cluster plan + map. |
/blog cluster plan --from strategy [path] |
Imports existing blog-strategy cluster build plan and validates against SERP data. |
/blog cluster execute [path-to-plan] |
Sequential blog-write calls with cluster context and auto-interlinks. |
Key references (load on demand)
references/semantic-clustering.md(SERP overlap analysis, intent classification, keyword universe expansion)references/cluster-architecture.md(hub-and-spoke specs, schema strategy, link-density rules)references/execution-workflow.md(execution order, context injection, scorecard, failure handling)
Cross-references to existing claude-blog skills
| Skill | When this skill calls it |
|---|---|
/blog strategy |
Upstream planning. plan --from strategy consumes its Cluster Build Plan tables. |
/blog write |
Per-post execution. Each spoke and the pillar are produced by blog-write with a prepended cluster-context block. |
/blog chart |
Invoked internally by blog-write for inline SVG charts. No direct call from this skill. |
/blog image |
Optional hero image generation per post (graceful fallback if nanobanana-mcp is not configured). |
/blog seo-check |
Recommended after execution for per-post on-page validation. |
/blog cannibalization |
Recommended after execution to confirm zero keyword overlap across the cluster. |
/blog schema |
Recommended after execution to add BreadcrumbList, ItemList, and Article schema. |
This skill never modifies files belonging to other skills. It calls them via the Task tool or as orchestrated sub-skills.
What ships with it
3 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.
- 9d ago First seen · 318 lines · 135 tokens per session scan A 3dcc8564a518
blog-cluster is a skill published in the GitHub repository Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo ago), licensed MIT. It adds 135 tokens to every session and 4,103 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to blog-cluster, differing in 43 lines, and is treated as a copy.
Other skills, from other repositories
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
geo
GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific…
geo-brand-mentions
Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.
geo-llmstxt
Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.
agent-readiness-scan
Use when a client audit, GEO/AI-visibility snapshot, or remediation re-scan needs the Cloudflare agent-readiness score from isitagentready.com — e.g. Theo client audits, "is the site agent-ready", markdown negotiation / MCP / llms.txt / Content-Signal checks, or tracking score deltas after Tier 0/1 fixes.
found-by-ai
Measure whether AI engines actually recommend a business when buyers ask. Runs the free live scan at areyoufoundbyai.com (no auth, 60s), reads the verdict and the rivals AI names instead, hands back the fix plan, and wires monitored sites into a fix-and-re-measure loop over MCP.