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 me-cedric/agent-compass --skill design-taste-skillsgit clone --depth 1 https://github.com/me-cedric/agent-compassWrote 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/me-cedric/agent-compass/design-taste-skills)<a href="https://agentmods.dev/skills/me-cedric/agent-compass/design-taste-skills"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/design-taste-skills/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/me-cedric/agent-compass/design-taste-skills"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/design-taste-skills.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.00040 | $0.00496 |
| Opus 5.5 | $0.00016 | $0.00198 |
| Sonnet 5.5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
design-taste-skills 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 10d 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.
What it actually says
design-taste-skills
Design skills are pinned upstream under the source id taste. Compass keeps no copy.
They do not mix. A dense product UI and a landing page need opposite advice. Pick one group and stay in it.
Install
Add the source id to upstream in .agents/compass.json. Then run ac sync. The source id is taste.
Pick the group
| Surface | Skills |
|---|---|
| Landing page, marketing site, portfolio | design-taste-frontend, and at most one of industrial-brutalist-ui or stitch-design-taste |
| Dense product UI, admin, dashboard | high-end-visual-design and minimalist-ui |
| An existing surface to rework | redesign-existing-projects |
| Brand system, logo, identity | brandkit |
| A mockup, screenshot or Figma frame to convert | image-to-code |
Do not use a landing-page skill and a product-UI skill in one project, unless the project has both surfaces. Say which surface you work on.
Give it a direction
Fix these items before you generate anything:
- The surface and its main job.
- A named style direction, such as editorial, Swiss or brutalist. "Clean and modern" is not a direction.
- The source of the palette and the type: the design system, a Figma token export, or a choice that you can defend.
- What must not change: tokens, component API, brand constraints.
If the project has a design system, the system wins. Use the skill to apply it well. When Figma is the source, run ui-conformance first.
Prove it
A design change is visible, so it needs visual proof at each viewport. Run ui-conformance.
A skill that says the result "looks expensive" is not proof.
A direction that fails contrast or keyboard navigation is not finished.
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.
- 10d ago Changed · -60 lines · -97 tokens per session 286b26469938
- 1mo ago First seen · 108 lines · 137 tokens per session scan A 2e8981a9fb36
design-taste-skills is a skill published in the GitHub repository me-cedric/agent-compass (3 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 496 once invoked, about $0.0002 per session on Opus 5.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
brand-landingpage
Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established…
web-design
Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.
mockuplm
Create visual UX mockups using HTML/CSS files (.mockup.html). Use when the user wants to design UI, wireframes, visual layouts, or plan features visually.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
tailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
ui-craft
Design, build, redesign, or modify browser-visible web interfaces with product-quality composition, visual systems, interaction states, responsive behavior, accessibility, and browser visual QA. Use for HTML, CSS, JavaScript, React, Vue, or Svelte pages and components, landing pages, dashboards, admin tools, settings…