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 joaoguirunas/team-os --skill seo-dataforseogit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/seo-dataforseo)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/seo-dataforseo"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/seo-dataforseo/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/joaoguirunas/team-os/seo-dataforseo"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/seo-dataforseo.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.00094 | $0.04128 |
| Opus 5.5 | $0.00038 | $0.01651 |
| Sonnet 5.5 | $0.00019 | $0.00826 |
| Haiku 4.5 | $0.00009 | $0.00413 |
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 20d 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
94% identical to seo-dataforseo — 47 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 — 395 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 (organic + images), 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 MCP server registered in the project's .mcp.json (or via claude mcp add dataforseo -e DATAFORSEO_USERNAME=<login> -e DATAFORSEO_PASSWORD=<password> -- npx -y dataforseo-mcp-server). The bundled scripts (dataforseo_merchant.py, cost tracking) read the same DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD environment variables. No installer script ships with this pack.
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 DataForSEO MCP server is not
configured and point to the setup above.
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)
Cost Guardrails
Before every DataForSEO MCP call, run cost estimation:
"${CLAUDE_PROJECT_DIR}/.claude/skills/seo/scripts/claude-seo" run dataforseo_costs.py check <endpoint> [--count N]
- If
"status": "approved"→ proceed with the API call - If
"status": "needs_approval"→ show the cost estimate to the user and ask for confirmation before proceeding - If
"status": "blocked"→ inform the user that the daily budget limit would be exceeded; do NOT proceed
After each API call completes, log the cost:
"${CLAUDE_PROJECT_DIR}/.claude/skills/seo/scripts/claude-seo" run dataforseo_costs.py log <endpoint> <actual_cost>
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.
- 20d ago Changed · -7 lines · -4 tokens per session 47757964a3eb
- 25d ago First seen · 402 lines · 98 tokens per session scan A 5f5b6240034e
seo-dataforseo is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 94 tokens to every session and 4,128 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to seo-dataforseo, differing in 47 lines, and is treated as a copy.
Other skills, from other repositories
jsonl-log-analyzer
Analyze large JSONL log files using schema-aware partitioned analysis. Discovers field schema, generates tailored jq extraction recipes, and orchestrates parallel chunk analysts with synthesis. Use when processing JSONL logs exceeding context limits, performing log analytics, or investigating incident logs.
orchestration-patterns
Apply proven orchestration patterns for agent teams including parallel specialists, pipelines, swarms, research+implementation, plan approval, and multi-file refactoring. Use when choosing a team structure, designing workflows, or implementing specific coordination patterns.
task-system
Manage shared task lists for agent teams including creating tasks, setting dependencies, claiming work, and tracking progress. Use when creating work items, building task pipelines, coordinating task ownership, or managing task dependencies.
spawn-backends
Configure how teammate agents run including in-process, tmux, and iTerm2 backends. Use when choosing a display mode, setting up split panes, troubleshooting backend issues, or configuring teammateMode.
error-handling
Debug and recover from agent team errors including common errors, hooks for quality gates, known limitations, and recovery strategies. Use when encountering team errors, enforcing quality gates with hooks, understanding limitations, or debugging agent issues.
messaging
Send messages between agents using SendMessage including direct messages, broadcasts, shutdown requests/responses, and plan approvals. Use when communicating between agents, understanding message formats, or handling structured protocol messages.