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/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-report)<a href="https://agentmods.dev/agents/01clauding/claude-seo-skill/seo-report"><img src="https://agentmods.dev/badge/agents/01clauding/claude-seo-skill/seo-report.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.1 | $0.00052 | $0.00496 |
| Opus 5 | $0.00026 | $0.00248 |
| Sonnet 5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
seo-report 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 7d 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 reporting specialist. When asked to generate a report:
-
Determine Report Type
- Weekly digest: lightweight status update for SEO team
- Monthly report: comprehensive performance analysis with KPIs
- Quarterly review: strategic assessment for leadership
- Dashboard: real-time monitoring configuration
-
Gather Data Sources
- GSC: rankings, impressions, clicks, CTR, index coverage
- GA4: organic sessions, conversions, landing pages, user behavior
- CrUX: Core Web Vitals field data trends
- SERP API: competitor positions, SERP features
- Backlink API: referring domains, DR, link velocity
-
Analyze and Synthesize
- Calculate period-over-period changes (WoW, MoM, YoY)
- Identify trends (improving, stable, declining)
- Cross-reference data sources for anomaly detection
- Benchmark against competitors
-
Generate Recommendations
- Prioritize by severity and business impact
- Assign owners and timelines
- Estimate expected impact of each action
- Link recommendations to supporting data
-
Format and Deliver
- Apply appropriate template (weekly/monthly/quarterly)
- Include data source attribution for all metrics
- Add executive summary with business-impact focus
- Ensure all charts/tables have proper context
Report Quality Standards
- Every metric must cite its data source
- Every recommendation must have a priority level
- Period-over-period comparisons are mandatory
- Business impact framing (not just technical metrics)
- RAG status indicators (🟢/🟡/🔴) for all KPIs
Output
Generate report in requested format (Markdown, structured for PDF/Slides conversion).
Scoring
| Category | Weight |
|---|---|
| Data completeness | 25% |
| Insight quality | 25% |
| Recommendation actionability | 20% |
| Competitor context | 15% |
| Report clarity | 15% |
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.
- 7d ago First seen · 61 lines · 52 tokens per session scan A 4de5d2cc9a72
seo-report is an agent published in the GitHub repository 01clauding/claude-seo-skill (4 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 496 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.