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 committed-aestheticgit 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/committed-aesthetic)<a href="https://agentmods.dev/skills/avelikiy/great_cto/committed-aesthetic"><img src="https://agentmods.dev/badge/skills/avelikiy/great_cto/committed-aesthetic/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/committed-aesthetic"><img src="https://agentmods.dev/badge/skills/avelikiy/great_cto/committed-aesthetic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 124 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 128 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.01625 |
| Opus 5 | $0.00047 | $0.00813 |
| Sonnet 5 | $0.00019 | $0.00325 |
| Haiku 4.5 | $0.00009 | $0.00162 |
Grade A, and why
committed-aesthetic 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 7d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A committed aesthetic beats a catalogue
The problem this exists for
ui-ux-pro-max ships 84 styles, 161 palettes and 57 font pairings, and
design-advisor is wired to all of it. The catalogue is not the bottleneck.
The bottleneck is that a catalogue lets a model pick, and an unconstrained pick is the modal one. Asked for a landing page with no brand, any model reaches for the same safe centre: a soft gradient, a large sans heading, three rounded cards with a left accent border, generous neutral grey. Every input in the training distribution votes for it. Nothing in a catalogue entry saying "Swiss minimalism — clean, grid-based, generous whitespace" is specific enough to override that, because that sentence describes the safe centre too.
Compare a rule from a committed aesthetic:
every dimension is
calc(fraction * 100vw)against a baseline width, so one page at 1024px reads as a perfect scaled-down of the same page at 1920px
You can check that. A design either obeys it or does not. That is the whole difference: a catalogue entry is a label, a committed aesthetic is a constraint.
The form
A committed-aesthetic skill has five parts. The first is the one that does the work.
1. Transferable DNA — numbered, specific, falsifiable
Between 8 and 14 rules. Each must be checkable by someone who was not in the room. Test every rule against this: could two designers disagree about whether a page obeys it? If yes, it is a vibe, rewrite it.
| Vibe (useless) | Constraint (usable) |
|---|---|
| "thin, elegant type" | "weights 100 or 300 only, never 400+" |
| "lots of whitespace" | "~60% of any above-the-fold area is empty" |
| "restrained motion" | "no shadows, no gradients, no bounce; one shadow exists in the system, on toasts" |
| "technical feel" | "product codes use en-dash U+2013, never hyphen" |
| "dark and dense" | "five surface steps, each ~5% apart; depth is a surface step, never a shadow" |
2. What this does NOT do — the IP boundary, as a table
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.
- 7d ago First seen · 132 lines · 94 tokens per session scan A d89dae2f252d
committed-aesthetic is a skill published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 1,625 once invoked, about $0.0005 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-09-03.
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.