seo-mcp: Skill for Claude Code

.agents/skills/seo-radar/SKILL.md

seo-radar is a skill for Claude Code, Codex from QexleOSS/seo-mcp. It costs 46 tokens per session (672 once invoked), scanned A, original, MIT.

A daily research workflow for understanding what people search for in a niche. It combines current trends, keyword suggestions, and snapshots of search-result pages into a Markdown file.

In plain words
What is it for?
Use it to find search topics, investigate keyword ideas, inspect search results, and prepare a daily niche brief.
Why use it?
It keeps these different kinds of search evidence together and distinguishes trends from estimates of search volume.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is QexleOSS/seo-mcp's own configuration. It tells Claude Code and Codex how to work on seo-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything seo-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to QexleOSS/seo-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/QexleOSS/seo-mcp/main/.agents/skills/seo-radar/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/QexleOSS/seo-mcp

Made for: Claude Code, Codex.

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.

agentmods badge for seo-radar

README.md
[![agentmods](https://agentmods.dev/badge/skills/qexleoss/seo-mcp/seo-radar/github.svg)](https://agentmods.dev/skills/qexleoss/seo-mcp/seo-radar)
Your own site
<a href="https://agentmods.dev/skills/qexleoss/seo-mcp/seo-radar"><img src="https://agentmods.dev/badge/skills/qexleoss/seo-mcp/seo-radar/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.

agentmods 80×15 button for seo-radar

Your own site · 80×15
<a href="https://agentmods.dev/skills/qexleoss/seo-mcp/seo-radar"><img src="https://agentmods.dev/badge/skills/qexleoss/seo-mcp/seo-radar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 672 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00672
Opus 5.5 $0.00018 $0.00269
Sonnet 5.5 $0.00009 $0.00134
Haiku 4.5 $0.00005 $0.00067

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

Security

Grade A, and why

seo-radar 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 2d 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.

.agents/skills/seo-radar/SKILL.md · 68 lines

How it starts

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

SEO Radar

Turns three live readings into one file per niche per day:

  • what people are searching for right now (get_trending)
  • which keyword candidates the autocomplete engines accept (get_keyword_research)
  • what the result page for a keyword looks like (get_serp_snapshot)

Every number in the file names the source it came from. A trend is not a volume estimate, and the file keeps that difference visible.

Run it

bunx @qexle/seo-mcp radar --niche "<topic>" --out radar-$(date +%F).md

Without --out the markdown goes to stdout, which is what an agent session wants. --seed "<keyword>" starts the keyword pass from a specific term instead of the niche phrase, and --limit sets how many rows each section keeps (default 8).

As an MCP server the same three tools are available directly:

{"tool": "get_trending", "arguments": {"niche": "seo tools", "geo": "US"}}
{"tool": "get_keyword_research", "arguments": {"seed": "technical seo audit", "depth": "quick"}}
{"tool": "get_serp_snapshot", "arguments": {"keyword": "technical seo audit"}}

Working method

  1. Pick the niche in the words a customer would type. "coffee shops in Berlin" beats "local coffee market".
  2. Read the trends section first. It says what is moving now, so the keyword pass asks about live demand rather than a frozen list.
  3. Use the keyword candidates as they are. The autocomplete rank is the engine's own order, so a candidate at rank 1 outranks a candidate at rank 6 without needing a score.
  4. Snapshot only the candidates that matter. Each snapshot is a live request.
  5. Write the file with the date in the name, so a later run can be compared against it.

Rules

  • Name the source for every figure. The file already does, and a summary written from it must as well.
  • Report the tools that came back silent. An engine that answered nothing is missing data, not zero demand.
  • Keep the difficulty score labelled as an estimate. It is a score built from the visible result page, not a search volume.
  • Do not add volume numbers. The keyless path has no volume source, and a made-up number is worse than a missing one.

Read the full file on GitHub · 68 lines

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.

  1. 2d ago First seen · 68 lines · 46 tokens per session scan A 2eaa7de95470

Subscribe to this mod's changes

seo-radar is a skill published in the GitHub repository QexleOSS/seo-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 672 once invoked, about $0.0002 per session on Opus 5.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-11-04.

Related

seo-radar compared with skills from other repositories

seo-radar next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
seo-radarQexleOSS/seo-mcpSkill03d agoMITA46Claude Code, Codex
gentech-blockrunBlockRunAI/blockrun-mcpSkill389yesterdayMITA46Claude Code, Codex
portainer-mcp-hygieneportainer/portainer-mcpSkill24115d agoMITA315Claude Code, Codex
hmem-releaseBumblebiber/hmemSkill246d agoMITA50Claude Code
disease-analysisdbcls/togomcpSkill212d agoMITA149Claude Code, Codex
research-article-analysisdbcls/togomcpSkill212d agoMITA147Claude Code, Codex
index-advisorDeepSQLAI/deepsqlSkill405d agoApache-2.0A32Claude Code, Codex