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-watchlistgit 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-watchlist)<a href="https://agentmods.dev/skills/zubair-trabzada/dataforseo-claude/seo-watchlist"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/dataforseo-claude/seo-watchlist/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-watchlist"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/dataforseo-claude/seo-watchlist.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.00059 | $0.00907 |
| Opus 5.5 | $0.00024 | $0.00363 |
| Sonnet 5.5 | $0.00012 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade B, and why
seo-watchlist 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 2mo 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.
3. `chmod 600 ~/.claude/skills/seo/.env` How it starts
The opening of the file, as written. The whole thing — 106 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 in this format:
login: [email protected]
password: their_api_password_here
When they reply:
- Parse
login:andpassword:from their message. - Write them to
~/.claude/skills/seo/.env:DATAFORSEO_LOGIN=<login> DATAFORSEO_PASSWORD=<password> chmod 600 ~/.claude/skills/seo/.env- Run a verification call:
~/.claude/skills/seo/scripts/keyword_research.py volume "test" - If verification succeeds (real JSON returned): tell the user "✅ Credentials verified. Running your command now..." and proceed with the original request.
- If status
40104 — Please verify your account: tell the user to verify their account at https://app.dataforseo.com/, then say "continue" to retry. - If any other auth error: ask them to double-check the API password (the long alphanumeric string from https://app.dataforseo.com/api-access — not their account login password).
Never echo credentials back to the user, never include them in tool output, and never commit them.
SEO Watchlist Skill
Powered by: DataForSEO API — SERP
google/organic/live/advancedfor live rank checks across the saved keyword set. Cost: ~$0.002 per keyword per check.
A simple file-based watchlist at ~/.claude/skills/seo/output/watchlist.json.
Schema
{
"domains": {
"example.com": {
"label": "Main site",
"keywords": ["seo audit tool", "keyword research", "..."],
"history": [
{"date": "2026-04-15", "rankings": [{"keyword": "...", "position": 8}, ...]},
{"date": "2026-04-22", "rankings": [{"keyword": "...", "position": 6}, ...]}
]
}
}
}
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.
- 2mo ago First seen · 106 lines · 59 tokens per session scan B 86a87dfc4843
seo-watchlist is a skill published in the GitHub repository zubair-trabzada/dataforseo-claude (175 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 907 once invoked, about $0.0002 per session on Opus 5.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.
seo-watchlist compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| seo-watchlistzubair-trabzada/dataforseo-claude | Skill | 175 | 5mo ago | MIT | B | 59 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |