Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/BestLemoon/codex-seonpx agentmods add skills/bestlemoon/codex-seo/seo-dataforseoWrote 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/bestlemoon/codex-seo/seo-dataforseo)<a href="https://agentmods.dev/skills/bestlemoon/codex-seo/seo-dataforseo"><img src="https://agentmods.dev/badge/skills/bestlemoon/codex-seo/seo-dataforseo.svg" alt="Measured on agentmods" 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.04033 |
| Opus 5 | $0.00064 | $0.02017 |
| Sonnet 5 | $0.00026 | $0.00807 |
| Haiku 4.5 | $0.00013 | $0.00403 |
Grade A, and why
seo-dataforseo 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 6d 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
83% identical to seo-dataforseo — 114 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DataForSEO: Live SEO Data (Extension)
Live search data via the DataForSEO MCP server. Provides real-time SERP results, keyword metrics, backlink profiles, on-page analysis, content analysis, business listings, AI visibility checking, and LLM mention tracking across 9 API modules with 79 MCP tools.
Prerequisites
This skill requires the DataForSEO extension to be installed:
./extensions/dataforseo/install.sh
Check availability: Before using any DataForSEO tool, verify the MCP server
is connected by checking if serp_organic_live_advanced or any DataForSEO tool
is available. If tools are not available, inform the user the extension is not
installed and provide install instructions.
API Credit Awareness
DataForSEO charges per API call. Be efficient:
- Prefer bulk endpoints over multiple single calls
- Use default parameters (US, English) unless user specifies otherwise
- Cache results mentally within a session; don't re-fetch the same data
- Warn user before running expensive operations (full backlink crawls, large keyword lists)
Quick Reference
| Command | What it does |
|---|---|
/seo dataforseo serp <keyword> |
Google organic SERP results |
/seo dataforseo serp-youtube <keyword> |
YouTube search results |
/seo dataforseo youtube <video_id> |
YouTube video deep analysis |
/seo dataforseo keywords <seed> |
Keyword ideas and suggestions |
/seo dataforseo volume <keywords> |
Search volume for keywords |
/seo dataforseo difficulty <keywords> |
Keyword difficulty scores |
/seo dataforseo intent <keywords> |
Search intent classification |
/seo dataforseo trends <keyword> |
Google Trends data |
/seo dataforseo backlinks <domain> |
Full backlink profile |
/seo dataforseo competitors <domain> |
Competitor domain analysis |
/seo dataforseo ranked <domain> |
Ranked keywords for domain |
/seo dataforseo intersection <domains> |
Keyword/backlink overlap |
/seo dataforseo traffic <domains> |
Bulk traffic estimation |
/seo dataforseo subdomains <domain> |
Subdomains with ranking data |
/seo dataforseo top-searches <domain> |
Top queries mentioning domain |
/seo dataforseo onpage <url> |
On-page analysis (Lighthouse + parsing) |
/seo dataforseo tech <domain> |
Technology stack detection |
/seo dataforseo whois <domain> |
WHOIS registration data |
/seo dataforseo content <keyword/url> |
Content analysis and trends |
/seo dataforseo listings <keyword> |
Business listings search |
/seo dataforseo ai-scrape <query> |
ChatGPT web scraper for GEO |
/seo dataforseo ai-mentions <keyword> |
LLM mention tracking for GEO |
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.
- 6d ago First seen · 394 lines · 128 tokens per session scan A 1a9abcc89d13
seo-dataforseo is a skill published in the GitHub repository BestLemoon/codex-seo (9 stars, last pushed 2mo ago), licensed MIT. It adds 128 tokens to every session and 4,033 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to seo-dataforseo, differing in 114 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…