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 avelikiy/great_cto --skill anydesigngit clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/avelikiy/great_cto/anydesign)<a href="https://agentmods.dev/skills/avelikiy/great_cto/anydesign"><img src="https://agentmods.dev/badge/skills/avelikiy/great_cto/anydesign/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/avelikiy/great_cto/anydesign"><img src="https://agentmods.dev/badge/skills/avelikiy/great_cto/anydesign.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.00214 | $0.02961 |
| Opus 5 | $0.00107 | $0.01481 |
| Sonnet 5 | $0.00043 | $0.00592 |
| Haiku 4.5 | $0.00021 | $0.00296 |
Grade A, and why
anydesign 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 6d 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
100% identical to anydesign — 0 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AnyDesign — Design analysis and documentation skill
Role and mindset
You act as a Design Systems Analyst: part visual detective, part systems designer, part frontend engineer. Your job is not to describe what you see — it's to diagnose the design: which decisions were deliberate, which patterns repeat, which tokens are operating under the surface, and what would be needed to reconstruct it.
Your primary audience is product designers and AI experience designers who need actionable
references, not poetic descriptions. You aim for a design.md that another AI (or a human)
can read and use to reconstruct the design with reasonable fidelity.
You work in the user's language. If they write in Spanish, respond in Spanish. If English, in English.
When to use which source
The skill supports three input types. Each has its own flow:
| Source | How to process it |
|---|---|
| Local image (PNG, JPG, WebP) | Direct multimodal vision. You "see" it and analyze it. |
| Website URL | Hybrid flow: HTML first via WebFetch, CSS variables extraction, screenshot via Playwright only if needed. |
| Figma link | Figma MCP: get_design_context, get_variable_defs, get_metadata, get_screenshot. |
If the user passes multiple sources at once (e.g., a URL + a manual screenshot), combine them: HTML and CSS for structure/classes/tokens, screenshot for final visual presentation.
Two modes: full analysis vs element copy
Before starting the workflow, determine the scope of the request:
- Full mode (default): the user wants the design of a page/file/system →
follow the Mandatory workflow below, output
design.md. - Element mode: the user wants ONE visual element — "copy this navbar",
"just the pricing card", "recreate this 3D illustration", "give me a prompt to
generate this graphic" → read
references/element-copy.mdand follow its E-steps, outputelement.md. Element mode reuses the capture flows (Step 2) scoped to the element, and classifies it ascode(reconstructable with HTML/CSS),asset(needs a generative image prompt), orhybrid(both).
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- LICENSE 1.1 KB
- references/analysis-framework.md 23 KB
- references/capture-flows.md 8.6 KB
- references/element-copy.md 13 KB
- references/output-template.md 19 KB
- references/token-extraction.md 9.9 KB
- requirements.txt 793 B
- scripts/capture_site.py 13 KB runs code
- scripts/check_contrast.py 6.2 KB runs code
- scripts/export_for_claude_design.py 43 KB runs code
- scripts/extract_colors.py 4.7 KB runs code
- scripts/extract_css_vars.py 8.6 KB runs code
- scripts/lint_design_md.py 12 KB runs code
- scripts/verify_design.py 12 KB runs code
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.
- 6d ago First seen · 245 lines · 214 tokens per session scan A 7834e1fc79a3
anydesign is a skill published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 214 tokens to every session and 2,961 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to anydesign, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
quality-review
After a PRD, spec, or plan, before implementation: hunt perceived-quality pitfalls (silent failures, missing loading/empty states, error recovery, state drift) that make a product feel cheap. Complements pitfall-verification.
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
fec-implement-from-design
A frontend implementation guide for turning designs or screenshots into reusable web pages and components.
fec-accessibility-check
A front-end accessibility review guide for checking whether websites and interfaces work for people with disabilities, including keyboard and screen-reader users. It uses WCAG 2.2 AA, a set of web accessibility guidelines, as its reference.
fec-storybook-component-doc
A workflow for documenting interface components in Storybook, a tool that displays UI components and their states in isolation. It covers stories, reusable setup wrappers, written documentation, interaction checks, accessibility checks, and visual baselines.