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-pagegit 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-page)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/seo-page"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/seo-page/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-page"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/seo-page.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.00094 | $0.00821 |
| Opus 5 | $0.00047 | $0.00411 |
| Sonnet 5 | $0.00019 | $0.00164 |
| Haiku 4.5 | $0.00009 | $0.00082 |
Grade A, and why
seo-page scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Fetch the page** (WebFetch, or `curl`-style retrieval of the raw HTML). For a How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-page
Family: seo Status: Stable
Purpose
The single-page analyzer: the same on-page, meta, schema, image, and internal-link
checks as a full audit, scoped to one URL, plus observable performance issues —
real Core Web Vitals field data only when seo-google is connected. Cheaper to
run and easier to act on for spot checks, pre-publish reviews, and "is this page
good?" questions. The free path (fetch + parse + score) is the whole product; paid
APIs only add live ranking and field-performance context.
Triggers
- "analyze this page" / "check this page" / "review this URL"
- "single URL SEO" / "check page SEO"
- "page-level analysis"
Inputs
- A single URL (or local HTML file)
- Optional: target keyword(s) for relevance scoring
Steps
- Fetch the page (WebFetch, or
curl-style retrieval of the raw HTML). For a local build, read the file directly. - On-page & meta — check: one descriptive
<title>(≤ ~60 chars), meta description (~150–160 chars), exactly one<h1>and a logical heading order, canonical tag, meta robots, and Open Graph / Twitter card tags. - Content quality — word count vs topical depth, target-keyword presence in
title/H1/early body (without stuffing), readability, and whether the page
answers the likely search intent. (Hand to
seo-contentfor deep E-E-A-T.) - Schema — detect JSON-LD; validate type appropriateness and required
properties; flag rich-result eligibility. (Delegate deeper work to
seo-schema.) - Images — alt text presence/quality, dimensions declared (CLS), modern formats (WebP/AVIF), and lazy-loading below the fold.
- Performance — note render-blocking resources and obvious payload issues.
If
seo-google(PageSpeed/CrUX) is available, pull real LCP/CLS/INP; otherwise report observable issues and say field data needsseo-google. - Internal links — count, descriptive anchor text, and whether the page links to/within relevant site sections.
- Optional enrichment — if the DataForSEO extension is configured, add live ranking/keyword context; otherwise state, in one line, what it would add.
- Render a compact report — findings grouped Critical / High / Medium / Low, each with a specific fix.
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 · 71 lines · 94 tokens per session scan A e39ca211bc3d
seo-page is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 94 tokens to every session and 821 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…