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 amirjahfar1/automate-seo-with-claude --skill seo-competitor-pagesgit clone --depth 1 https://github.com/amirjahfar1/automate-seo-with-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/amirjahfar1/automate-seo-with-claude/seo-competitor-pages)<a href="https://agentmods.dev/skills/amirjahfar1/automate-seo-with-claude/seo-competitor-pages"><img src="https://agentmods.dev/badge/skills/amirjahfar1/automate-seo-with-claude/seo-competitor-pages/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/amirjahfar1/automate-seo-with-claude/seo-competitor-pages"><img src="https://agentmods.dev/badge/skills/amirjahfar1/automate-seo-with-claude/seo-competitor-pages.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.00119 | $0.02532 |
| Opus 5 | $0.00060 | $0.01266 |
| Sonnet 5 | $0.00024 | $0.00506 |
| Haiku 4.5 | $0.00012 | $0.00253 |
Grade A, and why
seo-competitor-pages 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 12d 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.
This is a copy
88% identical to seo-competitor-pages — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example output: examples/seo-competitor-pages-linear-vs-jira-20260514/COMPARISON.md
Competitor Comparison & Alternatives Pages
Produce conversion-tuned landing pages targeting comparative-intent keywords ("X vs Y", "alternatives to X", "best X for Y"). The deliverable is a paste-ready page draft with feature matrix, balanced verdict, schema markup, and a CTA flow that converts comparison-stage traffic.
Page types this skill produces
- "X vs Y" head-to-head — direct comparison between two products/services. Target keyword:
[Product A] vs [Product B]. - "Alternatives to X" — listicle-format page positioning the user's product as one of N alternatives to a category leader. Target keyword:
[Competitor] alternativesoralternatives to [Competitor]. - "Best X for Y" — segmented best-of page targeting a use case or audience. Target keyword:
best [category] for [use case].
Prerequisites
- DataForSEO MCP server connected.
- Claude's
WebFetchtool available. - User provides: (a) the user's brand/product (the page's hero), (b) target competitor(s) — at least one, optionally up to 5 for an alternatives page, (c) page type (auto-detected from the keyword if user doesn't specify), (d) target country (default
us).
Process
-
Validate & determine page type
- From the user's input, detect: vs / alternatives / best-of.
- If page type unclear, ask the user. Don't guess silently.
-
Pull competitor context
mcp__dataforseo__dataforseo_labs_google_competitors_domain- For the user's domain, list top organic competitors by
common_keywordsoverlap. - Validate that the user's named competitor is in the list (or close).
- For the user's domain, list top organic competitors by
-
Pull keyword data per brand
mcp__dataforseo__dataforseo_labs_google_ranked_keywords- For the user's domain and each named competitor, pull top 100 organic keywords.
- Identify: keywords each brand owns exclusively, keywords both rank for, gaps.
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.
- 12d ago First seen · 169 lines · 119 tokens per session scan A 02e92d449465
seo-competitor-pages is a skill published in the GitHub repository amirjahfar1/automate-seo-with-claude (2 stars, last pushed 3mo ago), licensed MIT. It adds 119 tokens to every session and 2,532 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to seo-competitor-pages, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
seo-site-audit-pro
Flagship comprehensive SEO audit combining Ahrefs and GSC data in sequential waves with checkpoint saves. Use when user says "site audit pro", "full audit", "comprehensive audit", "audit with live data", "deep audit", "pro audit", "complete SEO audit", "run a full site audit", or "audit everything for this domain".…
seo-content
Content quality and E-E-A-T analysis with AI citation readiness assessment. Enhanced with live Ahrefs (actual keyword rankings, positions) and GSC (search query performance) data to validate static E-E-A-T analysis with real user behavior. Use when user says "content quality", "E-E-A-T", "content analysis"…
seo-core-web-vitals
Dedicated Core Web Vitals deep-dive: pull field data (CrUX / PageSpeed Insights), fall back to Lighthouse lab data, score LCP, INP, and CLS against Google's thresholds at the 75th percentile, and run per-metric diagnosis playbooks with concrete fixes. Use when user says "core web vitals", "CWV", "LCP", "INP", "CLS"…
seo-geo
Optimize content for AI Overviews (formerly SGE), ChatGPT web search, Perplexity, and other AI-powered search experiences. GEO analysis enriched with Ahrefs Brand Radar AI visibility data when available. Includes brand mention signals, AI crawler accessibility, llms.txt compliance, passage-level citability scoring…
seo-lighthouse-audit
Run a Lighthouse audit against any URL via the local Lighthouse CLI or the PageSpeed Insights API fallback, parse category scores and failed audits, and map every failed audit ID to its official Chrome docs page plus a one-line fix. Use when user says "lighthouse", "lighthouse audit", "run lighthouse", "lighthouse…
seo-llms-txt
Generate, validate, or audit llms.txt files for AI search visibility. Crawls site structure, generates spec-compliant Markdown index for LLMs. Use when user says "llms.txt", "llm txt", "AI crawlers", "generate llms", "LLM file", "AI readability file".