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 ZachArticulateV/designer-pro-and-seo --skill seo-competitor-pagesgit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/seo-competitor-pages)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/seo-competitor-pages"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/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/zacharticulatev/designer-pro-and-seo/seo-competitor-pages"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/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.00072 | $0.00613 |
| Opus 5 | $0.00036 | $0.00307 |
| Sonnet 5 | $0.00014 | $0.00123 |
| Haiku 4.5 | $0.00007 | $0.00061 |
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 13d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-competitor-pages
Family: seo Status: Stable
Purpose
Generate the comparison and alternatives content types — bottom-of-funnel, high-intent, often high-CTR pages that frequently outrank top-of-funnel content for buyer-intent queries. Produces the page, its feature matrix, validated schema, and a conversion-optimized layout.
Triggers
- "comparison page" / "vs page" / "X vs Y" / "versus"
- "alternatives page" / "alternative to"
- "compare competitors" / "competitor comparison"
Inputs
- Target product/service and the competitor(s) (user-named, or from provided pages)
- Page type: comparison ("X vs Y") | alternatives ("alternatives to X")
- Brand positioning / the honest angle you win on
Steps
- Gather facts. Use competitor pages the user provides (or
design-researchwhen available) to extract real feature/pricing data — never invent competitor facts (legal + trust risk). - Build the matrix. Score both sides on the criteria buyers actually weigh; be fair (one-sided hit pieces lose trust and links).
- Draft the page (hand copy to
copywriting): decisive H1, an at-a-glance verdict, the feature matrix, use-case fit ("choose X if…, choose Y if…"), and an FAQ section. - Add schema via
seo-schema: Product/SoftwareApplication, Review/ AggregateRating (only with real ratings), and BreadcrumbList. Note: FAQ markup is still valid for AI/semantic context but no longer yields a Google rich result (deprecated 2026-05-07) — don't promise an FAQ snippet. - Conversion layer. One primary CTA, decision-aid widget, trust signals near
the verdict (apply
design-cro). - Render the page (HTML/markdown) + the matrix data + embedded schema.
Outputs
- Generated comparison/alternatives page (HTML or markdown)
- Feature-matrix data + validated JSON-LD
- Conversion-optimized layout notes
Dependencies
seo-schema(schema generation/validation);copywriting(page copy);design-cro(conversion). Optional:design-research(competitor facts).
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.
- 13d ago First seen · 63 lines · 72 tokens per session scan A 46a994267c43
seo-competitor-pages is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 613 once invoked, about $0.0004 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 skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…
engineering-onboarding
Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…