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 zubair-trabzada/dataforseo-claude --skill seogit clone --depth 1 https://github.com/zubair-trabzada/dataforseo-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/zubair-trabzada/dataforseo-claude/seo)<a href="https://agentmods.dev/skills/zubair-trabzada/dataforseo-claude/seo"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/dataforseo-claude/seo/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/zubair-trabzada/dataforseo-claude/seo"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/dataforseo-claude/seo.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.00113 | $0.03258 |
| Opus 5 | $0.00056 | $0.01629 |
| Sonnet 5 | $0.00023 | $0.00652 |
| Haiku 4.5 | $0.00011 | $0.00326 |
Grade B, and why
seo scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
I'll save them securely to ~/.claude/skills/seo/.env (chmod 600) and run How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Agency Killer — Claude Code Skill (April 2026)
Philosophy: One command in, real Google data out. No browsing, no scraping, no guesswork — every metric below comes straight from DataForSEO's live APIs.
Phase 0: First-Run Setup Check (MANDATORY — run before ANY command)
Before doing anything with a /seo ... request, run this check. Do not
skip it, even if the user just wants a quick command.
Step 1 — Read the credentials file:
cat ~/.claude/skills/seo/.env 2>/dev/null
Step 2 — Decide if credentials are configured:
The .env is NOT configured if any of these are true:
- The file doesn't exist
DATAFORSEO_LOGINis missing or contains the literal stringyour_login_email_hereDATAFORSEO_PASSWORDis missing or contains the literal stringyour_api_password_here
Step 3a — If credentials ARE configured: continue to the requested command, no message needed.
Step 3b — If credentials are NOT configured: STOP. Do not run the requested command. Instead, paste exactly this setup wizard to the user:
🔧 DataForSEO API Setup Required
This skill needs DataForSEO API credentials to fetch real Google SEO data.
One-time setup, takes 60 seconds:
Step 1 — Sign up free (includes $1 trial credit, ~10 full audits):
https://l.dataforseo.com/4epETnH
Step 2 — After verifying your email, open API Access:
https://app.dataforseo.com/api-access
Step 3 — Copy your API Login (your email) and API Password
(the long alphanumeric string under "API password")
Step 4 — Paste both back to me in this exact format:
login: [email protected]
password: 1adc9025dc1a3e86
I'll save them securely to ~/.claude/skills/seo/.env (chmod 600) and run
your original command immediately after.
Then WAIT for the user's reply with credentials.
Step 4 — When the user pastes credentials:
- Parse
login:andpassword:from their message (handleLogin:,Password:, email-only, or just two lines as well — be lenient) - Write them to
~/.claude/skills/seo/.envusing this format:
What ships with it
10 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.
- schema/audit_input.example.json 2.4 KB
- scripts/backlinks.py 4.2 KB runs code
- scripts/dataforseo_client.py 6.9 KB runs code
- scripts/domain_overview.py 4.4 KB runs code
- scripts/generate_pdf_report.py 9.8 KB runs code
- scripts/keyword_research.py 4.2 KB runs code
- scripts/on_page_audit.py 3.9 KB runs code
- scripts/preflight.sh 1.9 KB runs code
- scripts/prospect_finder.py 10 KB runs code
- scripts/serp_check.py 4.4 KB runs code
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 · 335 lines · 113 tokens per session scan B b7bc86c44d7b
seo is a skill published in the GitHub repository zubair-trabzada/dataforseo-claude (154 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 3,258 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…