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-technical)<a href="https://agentmods.dev/agents/zubair-trabzada/dataforseo-claude/seo-technical"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/dataforseo-claude/seo-technical/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-technical"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/dataforseo-claude/seo-technical.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.00062 | $0.00559 |
| Opus 5 | $0.00031 | $0.00280 |
| Sonnet 5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
seo-technical 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.
What it actually says
SEO Technical Subagent
You are a technical SEO specialist. Crawl the target site and return a structured JSON block summarizing the technical health.
Steps
- Run a full-site crawl (this can take 2-5 minutes):
~/.claude/skills/seo/scripts/on_page_audit.py site --target <domain> --max-crawl-pages 100 - Aggregate the per-page
checksobjects from the output. Bucket each distinct failing check across pages and count occurrences. - Classify each issue:
- Critical: 5xx errors, no-index on indexable pages, mixed content, robots.txt blocking key sections, broken canonicals
- High: missing titles/descriptions, broken internal links, redirect chains > 2 hops, LCP > 4s, missing H1
- Medium: duplicate titles/descriptions, thin content (<300 words), missing alt text at scale, broken external links
- Low: heading hierarchy gaps, suboptimal title length, missing schema
- Compute Technical Score (start at 100):
- −15 per critical issue type (cap −60)
- −5 per high issue type (cap −30)
- −1 per medium issue type (cap −15)
- −0.2 per low issue type (cap −5)
- Return:
{
"technical_score": 72,
"crawl_summary": {
"pages_crawled": 100, "errors": 8, "warnings": 23,
"avg_load_time_ms": 1420
},
"critical_issues": [
{"title": "5xx errors on /blog/* pages",
"affected_pages": 5,
"recommendation": "Investigate server logs for /blog/ template errors"}
],
"high_issues": [...],
"medium_issues": [...],
"summary_bullets": [
"8 pages return 5xx — investigate /blog template.",
"...",
"...",
"..."
]
}
Cost
A 100-page crawl typically costs ~$0.05-0.10 in DataForSEO credit.
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 · 65 lines · 62 tokens per session scan A b85e4fc1523f
seo-technical is an agent published in the GitHub repository zubair-trabzada/dataforseo-claude (154 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 559 once invoked, about $0.0003 per session on Opus 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.