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 Thibaultbm/claude-seo-geo --skill seo-content-bloggit clone --depth 1 https://github.com/Thibaultbm/claude-seo-geoWrote 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/thibaultbm/claude-seo-geo/seo-content-blog)<a href="https://agentmods.dev/skills/thibaultbm/claude-seo-geo/seo-content-blog"><img src="https://agentmods.dev/badge/skills/thibaultbm/claude-seo-geo/seo-content-blog/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/thibaultbm/claude-seo-geo/seo-content-blog"><img src="https://agentmods.dev/badge/skills/thibaultbm/claude-seo-geo/seo-content-blog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 159 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00110 | $0.05296 |
| Opus 5 | $0.00055 | $0.02648 |
| Sonnet 5 | $0.00022 | $0.01059 |
| Haiku 4.5 | $0.00011 | $0.00530 |
Grade A, and why
seo-content-blog 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Blog Content That Ranks and Gets Cited
Write or rewrite blog articles on a 12-element skeleton (field methodology from 115+ agency audits, layered with 2024-2026 citation research) so the same article ranks in Google and gets extracted as an answer by ChatGPT, Perplexity, and Google AI Overviews.
Company knowledge first (Obsidian)
If the working environment contains an Obsidian vault or any local knowledge base (a folder of .md notes, often with a .obsidian directory), read the relevant notes before acting: brand and product facts, target keywords, competitors, and the SEO action log of what was already tried. Ground every recommendation in that context instead of asking the user for facts the vault already holds. At the end of the session, append the actions taken to the vault's SEO action log so the next session starts informed. Vault structure, read-first and write-back protocols: the obsidian-brain skill.
When to use
- Writing a new blog article from a keyword, topic, or brief.
- Rewriting or refreshing a published post that decayed or never ranked.
- Reviewing a human-written or AI-generated draft before publication.
- Producing an outline or content brief for a writer.
- Planning publication cadence for a blog launch or an established site.
Route adjacent jobs to their own skills:
- Choosing the target keyword, mapping intent, splitting overlapping topics: seo-keyword-research.
- Product, service, or collection page copy: seo-content-product-page, seo-content-service-page, seo-content-collection-page.
- Site-level link routing and silos: seo-internal-linking. Full site diagnosis: seo-geo-audit.
Workflow
Step 1. Lock the target
Confirm before writing:
- Primary keyword and the intent behind it (informational or commercial investigation).
- Language and market: a French SERP and a US SERP rarely reward the same article.
- The commercial pages this article must support with internal links.
- Whether an existing article already covers this intent. If yes, rewrite it instead of creating a new one.
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 · 304 lines · 110 tokens per session scan A e2669248604c
seo-content-blog is a skill published in the GitHub repository Thibaultbm/claude-seo-geo (16 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 5,296 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-30.
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.