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/build-with-dhiraj/ai-workflow-framework-portability-kitnpx agentmods add skills/build-with-dhiraj/ai-workflow-framework-portability-kit/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/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-dataforseo)<a href="https://agentmods.dev/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-dataforseo"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/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/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-dataforseo"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/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.00144 | $0.04009 |
| Opus 5 | $0.00072 | $0.02005 |
| Sonnet 5 | $0.00029 | $0.00802 |
| Haiku 4.5 | $0.00014 | $0.00401 |
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 10d 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 — 26 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 — 404 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 10 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)
Cost Guardrails
Before every DataForSEO MCP call, run cost estimation:
python scripts/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:
python scripts/dataforseo_costs.py log <endpoint> <actual_cost>
User commands for cost management:
/seo dataforseo costs today→ show today's spending breakdown/seo dataforseo costs summary→ show 7-day spending history/seo dataforseo costs config --mode threshold --threshold 0.50→ configure approval mode
Load references/cost-tiers.md for the full pricing table, budget presets, and cost reduction tips.
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.
- 10d ago First seen · 404 lines · 144 tokens per session scan A 11b59b1ba689
seo-dataforseo is a skill published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (4 stars, last pushed 28d ago), licensed MIT. It adds 144 tokens to every session and 4,009 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to seo-dataforseo, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
hf-cloud-sagemaker-production-defaults
Implement a production SageMaker endpoint with autoscaling, CloudWatch alarms, and tags. Use after the serving image and IAM role are known; use the deployment planner first when architecture is undecided.
code-review
Review a pull request or a set of code changes for bugs, logic errors, and project-convention violations using a confidence-filtered, multi-agent process. Use this skill when the user asks to review a PR, audit pending changes, or inspect a diff for problems before merging.
codeql
Run CodeQL database creation and security queries, add data-extension models, or process CodeQL SARIF. Use when CodeQL is explicitly requested; use security-review for a broader manual security review.
sarif-parsing
Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners. Triggers on "parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", or "process sarif output". Handles filtering, deduplication, format conversion, and CI/CD integration of SARIF data. Does NOT…
security-review
Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…
agents-md-improver
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or…