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 seo-emailgit 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-email)<a href="https://agentmods.dev/skills/zubair-trabzada/dataforseo-claude/seo-email"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/dataforseo-claude/seo-email/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-email"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/dataforseo-claude/seo-email.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.00063 | $0.01127 |
| Opus 5 | $0.00032 | $0.00563 |
| Sonnet 5 | $0.00013 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
seo-email scanned grade A 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 rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
When they reply, parse `login:` and `password:`, write to `~/.claude/skills/seo/.env` (chmod 600), verify with `keyword_research.py volume "test"`, and proceed only after success. Never echo credentials. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Credential Preflight (REQUIRED — run BEFORE anything else)
Before running any of the steps below, always invoke the shared preflight check:
~/.claude/skills/seo/scripts/preflight.sh
If exit code is 0: credentials are configured — proceed with the rest of this skill silently.
If exit code is 2: the script prints the DataForSEO setup wizard to stdout. STOP, display that wizard to the user verbatim, and wait for them to paste credentials.
When they reply, parse login: and password:, write to ~/.claude/skills/seo/.env (chmod 600), verify with keyword_research.py volume "test", and proceed only after success. Never echo credentials.
SEO Cold Email Drafter
Powered by: Reads the audit JSON produced by
/seo audit(built from live DataForSEO API data). No new API calls — purely a drafting step.
Prerequisite
/seo audit <domain> must have run first and saved
~/.claude/skills/seo/output/<domain>-audit.json. If that file doesn't exist,
tell the user to run the audit first.
Inputs
The user provides a domain:
/seo email acmeplumbing.com/seo email <domain>
Optionally they can supply their own name/signature — otherwise use a generic placeholder.
Workflow
- Read
~/.claude/skills/seo/output/<domain>-audit.json - Pick the 2-3 most impactful findings from
audit.issues— prioritize critical and high-priority issues that have clear business impact (lost traffic, lost revenue, broken pages indexable). - Pull the single highest-leverage keyword opportunity from
audit.top_keywords— ideally one where they currently rank position 4-30 with decent volume and CPC. Compute its estimated monthly value:search_volume × CPC × 0.3(rough CTR for that position band). - Draft an email that:
- Has a short, specific subject that references their domain or the issue (not "I do SEO")
- Opens by referencing something specific you noticed (not "I came across your website")
- Lists 2-3 specific findings in bullet form — concrete, not generic ("you're missing meta descriptions on 12 service pages" not "your SEO needs work")
- Quantifies the value of one specific opportunity in dollars
- Offers to send the full PDF audit as a soft ask (no hard pitch)
- Ends with a low-pressure sign-off
- Output the email in this format (copy-pasteable):
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 · 100 lines · 63 tokens per session scan A 9fb91d913b9b
seo-email is a skill published in the GitHub repository zubair-trabzada/dataforseo-claude (154 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,127 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A 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…