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 design-crogit 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/design-cro)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/design-cro"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-cro/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/design-cro"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-cro.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.00114 | $0.00690 |
| Opus 5 | $0.00057 | $0.00345 |
| Sonnet 5 | $0.00023 | $0.00138 |
| Haiku 4.5 | $0.00011 | $0.00069 |
Grade A, and why
design-cro 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-cro
Family: design Status: Stable
Purpose
A dedicated CRO skill. Runs a heuristic review of a landing page or funnel against established conversion principles and produces a prioritized list of conversion-killing issues with specific fixes. Works on a URL or local HTML with no external tools; Playwright optionally adds in-browser checks (thumb zones, real interaction).
Reviews against: CTA hierarchy (one primary), above-fold weight, form friction, trust signals near the decision, copy clarity (benefit-led, 3-second headline), decision fatigue, and mobile reality.
Triggers
- "cro" / "conversion review" / "improve conversions"
- "why isn't this converting"
- "landing page review" / "funnel review"
- "checkout friction review"
Inputs
- Target URL or local build path
- Conversion goal (lead form / signup / purchase / call)
- Target audience and page type (landing | pricing | checkout | signup | contact)
Steps
- Get the page. Fetch the URL or read the local HTML (this is the free path).
- Walk the heuristic checklist, cross-referencing
data/ux-rules.csv(theconversionandctatagged rules): is there exactly one primary CTA? Is the value prop above the fold? How many form fields? Are trust signals near the CTA? Does the headline read in ~3 seconds? Any decision fatigue / competing actions? - Optional in-browser pass. If Playwright is available, check thumb-zone reachability and real interaction; otherwise note that as a manual check.
- Score each finding by Impact (high/med/low) and Fix Effort (high/med/low).
- Render the findings ordered by Impact ÷ Effort, each with a specific fix.
For copy fixes, hand to
copywriting.
Outputs
- CRO report: prioritized fix list, each tagged Impact + Effort, ordered by leverage
- Specific, actionable recommendation per finding
Dependencies
- None required (heuristic review of provided HTML/URL);
data/ux-rules.csvfor the conversion/CTA rule set - Playwright (optional — adds in-browser thumb-zone/interaction checks; free path: manual thumb-zone inspection of the fetched HTML, noted in the report)
copywriting(optional — drafts copy fixes; free path: inline copy recommendation per finding)
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 · 66 lines · 114 tokens per session scan A ff2adfa43f46
design-cro is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 114 tokens to every session and 690 once invoked, about $0.0006 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…