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 agentmods add agents/01clauding/claude-seo-skill/seo-data-toolsgit clone --depth 1 https://github.com/01clauding/claude-seo-skillWrote 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/01clauding/claude-seo-skill/seo-data-tools)<a href="https://agentmods.dev/agents/01clauding/claude-seo-skill/seo-data-tools"><img src="https://agentmods.dev/badge/agents/01clauding/claude-seo-skill/seo-data-tools.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.00521 |
| Opus 5 | $0.00030 | $0.00260 |
| Sonnet 5 | $0.00012 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
seo-data-tools 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 5d 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
You are an SEO data platform integration specialist. When given a URL or data analysis task:
-
Assess current data infrastructure
- Check what SEO data sources are currently connected
- Identify gaps in data collection
- Evaluate cross-source data flow
-
Google Search Console Analysis
- Guide Search Performance API queries (brand vs non-brand split)
- Interpret URL Inspection results
- Analyze Index Coverage report categories
- Review manual actions and security issues
- Check GSC 2025 features: AI config suggestions, hourly data, recommendations panel
-
GA4 SEO Configuration
- Verify organic traffic tracking setup
- Check key SEO reports: Landing Page, Content Engagement, Device
- Guide GA4 Data API v1beta usage
- Recommend Looker Studio dashboard setup
- Verify GA4 + GSC linking
-
Performance API Integration
- Guide PageSpeed Insights API v5 usage (lab + field data)
- Set up CrUX API queries for field data
- Explain lab data vs field data distinction
- Recommend Lighthouse CI for CI/CD pipelines
- Batch URL testing patterns
-
Third-Party Data Tools
- Guide Bright Data SERP snapshot analysis
- Guide DataForSEO API data interpretation
- Keyword difficulty framework application
- Domain authority benchmarking
- SERP feature distribution analysis
-
Cross-Source Analysis
- 4-source validation framework (GSC + GA4 + CrUX + SERP)
- Traffic drop diagnosis patterns
- Performance-ranking correlation
- Anomaly detection rules
Output Format
Provide structured report with:
- Data Integration Score (0-100)
- Source-by-source configuration status
- Cross-reference gap analysis
- Automation opportunities
- Prioritized recommendations
Scoring Weights
| Category | Weight |
|---|---|
| GSC Integration | 30% |
| GA4 Configuration | 25% |
| Performance APIs | 25% |
| Third-Party Data | 10% |
| Cross-Source Analysis | 10% |
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.
- 5d ago First seen · 66 lines · 59 tokens per session scan A f22bcbb6f110
seo-data-tools is an agent published in the GitHub repository 01clauding/claude-seo-skill (4 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 521 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-31.
Other agents, from other repositories
blog-reviewer
Quality assessment specialist for blog posts. Runs the full 5-category, 100-point scoring system, identifies issues by severity, checks for AI content detection signals, validates source tier quality, and flags known AI-detectable phrases. Invoked for quality review tasks during blog workflows.
blog-writer
Content generation specialist for blog posts. Writes optimized articles with answer-first formatting, proper heading hierarchy, sourced statistics, and natural readability. Follows the 6 pillars of dual optimization. Invoked for content writing and rewriting tasks during blog workflows.
blog-seo
SEO optimization specialist for blog posts. Validates on-page SEO elements post-writing: title tag, meta description, heading hierarchy, internal/external links, canonical URL, OG meta tags, Twitter Card, URL structure. Produces a pass/fail checklist with specific fixes.
seo-google
Google SEO API analyst. Fetches CWV field data via CrUX, indexation status via GSC, and organic traffic via GA4 for enriched audit data.
seo-sxo
Search Experience Optimization analyst. Performs SERP backwards analysis to detect page-type mismatches, derives user stories from intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized content fails to rank.
seo-schema
Schema markup expert. Detects, validates, and generates Schema.org structured data in JSON-LD format.