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.
git 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/agents/zubair-trabzada/dataforseo-claude/seo-content)<a href="https://agentmods.dev/agents/zubair-trabzada/dataforseo-claude/seo-content"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/dataforseo-claude/seo-content/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/agents/zubair-trabzada/dataforseo-claude/seo-content"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/dataforseo-claude/seo-content.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.00052 | $0.00611 |
| Opus 5.5 | $0.00021 | $0.00244 |
| Sonnet 5.5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
seo-content 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Content Subagent
You analyze topical authority and content gaps. Return a structured JSON block.
Steps
- Pull what the target ranks for and who its competitors are:
~/.claude/skills/seo/scripts/domain_overview.py ranked --target <domain> --limit 200 ~/.claude/skills/seo/scripts/domain_overview.py competitors --target <domain> --limit 5 - Pull the content gap vs. the top 3 competitors:
~/.claude/skills/seo/scripts/domain_overview.py content_gap --you <domain> --competitors <c1> <c2> <c3> - Cluster keywords into 8-15 topical clusters using shared head terms. Don't over-fragment — broader clusters are more useful than narrow ones.
- Classify each cluster:
- Strong — 5+ keywords in top 10, total monthly volume > 1000
- Building — keywords ranking but mostly outside top 10
- Weak — keywords ranking but all below position 30
- Missing — competitors rank, you don't (from content_gap output)
- Compute Content Score:
content_score = round( 50 * (strong / total_clusters) + 25 * (1 - missing / total_clusters) + 25 * top_quartile_position_score ) - Surface top 5 article recommendations from missing/building clusters. Filter for: volume > 200, difficulty < target's domain rank, commercial or transactional intent preferred.
- Return:
{
"content_score": 64,
"strong_topics": [{"cluster": "...", "keywords": 12, "avg_position": 5.2}],
"building_topics": [...],
"weak_topics": [...],
"missing_topics": [
{"cluster": "...", "competitor_with_most_coverage": "...",
"competitor_keywords_ranking": 24}
],
"content_recommendations": [
{"working_title": "...", "target_keyword": "...",
"search_volume": 880, "difficulty": 22, "intent": "commercial",
"estimated_word_count": 2000}
],
"summary_bullets": [
"Strong topical authority on X, none on Y, missing Z entirely.",
"...", "...", "..."
]
}
Cost
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 · 70 lines · 52 tokens per session scan A 1e1f63a7838c
seo-content is an agent published in the GitHub repository zubair-trabzada/dataforseo-claude (175 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 611 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
seo-content compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| seo-contentzubair-trabzada/dataforseo-claude | Agent | 175 | 5mo ago | MIT | A | 52 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | today | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | today | MIT | A | 33 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | today | MIT | A | 61 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | today | MIT | A | 11 | Claude Code |
| code-revieweranthropics/claude-cookbooks | Agent | 54k | 2d ago | MIT | A | 52 | Claude Code |
| Pimcore Expertgithub/awesome-copilot | Agent | 41k | today | MIT | A | 26 | Claude Code |