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 amirjahfar1/automate-seo-with-claude --skill seo-keyword-nichegit clone --depth 1 https://github.com/amirjahfar1/automate-seo-with-claudeWrote 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/amirjahfar1/automate-seo-with-claude/seo-keyword-niche)<a href="https://agentmods.dev/skills/amirjahfar1/automate-seo-with-claude/seo-keyword-niche"><img src="https://agentmods.dev/badge/skills/amirjahfar1/automate-seo-with-claude/seo-keyword-niche/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/amirjahfar1/automate-seo-with-claude/seo-keyword-niche"><img src="https://agentmods.dev/badge/skills/amirjahfar1/automate-seo-with-claude/seo-keyword-niche.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.00128 | $0.03088 |
| Opus 5 | $0.00064 | $0.01544 |
| Sonnet 5 | $0.00026 | $0.00618 |
| Haiku 4.5 | $0.00013 | $0.00309 |
Grade A, and why
seo-keyword-niche 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.
This is a copy
86% identical to seo-keyword-niche — 18 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example output: examples/seo-keyword-niche-espresso-machine-reviews-20260514/KEYWORD-NICHE-PLAN.md
Keyword Niche
Mine the long tail for content opportunities. Pulls longtail variants, question-intent keywords, related keywords, and SERP samples to find under-served niche keywords; clusters them by intent; proposes a content tier (template + URL pattern + sample pages + thin-content quality gates) that can be published programmatically or as a steady editorial cadence.
Prerequisites
- DataForSEO MCP server connected.
- User provides: a seed topic (e.g. "running shoes", "tax preparation"), or 2–5 seed keywords. Target country (default
us). Optional: minimum volume threshold (default: 50/mo for niche skill — lower thanseo-keyword-cluster's 100), maximum KD (default: 40 for accessibility).
Process
-
Validate & preflight
- Confirm seeds make sense (not too broad, not branded, not single-letter).
- DataForSEO bills per call; this run issues ~N calls. Use the documented
limit/filtersparams to cap. This skill is heavier than most: pulling longtail at depth issues more calls than pulling head terms.
-
Longtail expansion
mcp__dataforseo__dataforseo_labs_google_keyword_ideas- For each seed: pull longtail variants (typically 3+ words, lower individual volume, lower KD).
- Target: 200–500 longtail candidates per seed.
-
Question expansion
mcp__dataforseo__dataforseo_labs_google_keyword_ideas(filter to interrogatives: who/what/why/how/can/does/is/are…)- For each seed: pull question-phrased keywords.
- These are gold for content mining — explicit user intent in the keyword.
-
Related expansion
mcp__dataforseo__dataforseo_labs_google_related_keywordsandmcp__dataforseo__dataforseo_labs_google_keyword_suggestions- For each seed: pull related + similar keywords.
- Catches semantic neighbours that longtail expansion missed.
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 · 179 lines · 128 tokens per session scan A 834c4040f358
seo-keyword-niche is a skill published in the GitHub repository amirjahfar1/automate-seo-with-claude (2 stars, last pushed 3mo ago), licensed MIT. It adds 128 tokens to every session and 3,088 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to seo-keyword-niche, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
seo-site-audit-pro
Flagship comprehensive SEO audit combining Ahrefs and GSC data in sequential waves with checkpoint saves. Use when user says "site audit pro", "full audit", "comprehensive audit", "audit with live data", "deep audit", "pro audit", "complete SEO audit", "run a full site audit", or "audit everything for this domain".…
seo-content
Content quality and E-E-A-T analysis with AI citation readiness assessment. Enhanced with live Ahrefs (actual keyword rankings, positions) and GSC (search query performance) data to validate static E-E-A-T analysis with real user behavior. Use when user says "content quality", "E-E-A-T", "content analysis"…
seo-core-web-vitals
Dedicated Core Web Vitals deep-dive: pull field data (CrUX / PageSpeed Insights), fall back to Lighthouse lab data, score LCP, INP, and CLS against Google's thresholds at the 75th percentile, and run per-metric diagnosis playbooks with concrete fixes. Use when user says "core web vitals", "CWV", "LCP", "INP", "CLS"…
seo-geo
Optimize content for AI Overviews (formerly SGE), ChatGPT web search, Perplexity, and other AI-powered search experiences. GEO analysis enriched with Ahrefs Brand Radar AI visibility data when available. Includes brand mention signals, AI crawler accessibility, llms.txt compliance, passage-level citability scoring…
seo-lighthouse-audit
Run a Lighthouse audit against any URL via the local Lighthouse CLI or the PageSpeed Insights API fallback, parse category scores and failed audits, and map every failed audit ID to its official Chrome docs page plus a one-line fix. Use when user says "lighthouse", "lighthouse audit", "run lighthouse", "lighthouse…
seo-llms-txt
Generate, validate, or audit llms.txt files for AI search visibility. Crawls site structure, generates spec-compliant Markdown index for LLMs. Use when user says "llms.txt", "llm txt", "AI crawlers", "generate llms", "LLM file", "AI readability file".