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 korbinjoe/TeemAI --skill design-taste-frontendgit clone --depth 1 https://github.com/korbinjoe/TeemAIWrote 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/korbinjoe/teemai/design-taste-frontend)<a href="https://agentmods.dev/skills/korbinjoe/teemai/design-taste-frontend"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/design-taste-frontend/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/korbinjoe/teemai/design-taste-frontend"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/design-taste-frontend.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.00043 | $0.00496 |
| Opus 5 | $0.00022 | $0.00248 |
| Sonnet 5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
design-taste-frontend 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 11d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-taste-frontend
Use this skill whenever an agent is asked to design, implement, or review a frontend experience.
Operating stance
- Start from the user's real workflow, not a decorative page template.
- Preserve the existing product's design system unless the task is explicitly a redesign.
- Prefer dense, calm, scannable interfaces for operational tools.
- Build the actual usable surface first; do not make a marketing landing page unless the user asked for one.
- Make every control and state that the target user would naturally expect.
Visual standards
- Use clear hierarchy, restrained spacing, and stable responsive constraints.
- Avoid nested cards, one-note palettes, generic gradient backgrounds, floating decorative blobs, and oversized hero typography inside compact panels.
- Use icons for common toolbar actions when the project already has an icon library.
- Keep cards at modest radius unless the local design system says otherwise.
- Ensure text fits in buttons, cards, tables, sidebars, and mobile layouts.
- Do not let hover states, counters, labels, loading text, or dynamic content resize fixed-format UI such as boards, grids, and toolbars.
Interaction standards
- Use tabs for alternate views, segmented controls for mode switching, toggles for binary settings, menus for option sets, and sliders or inputs for numeric values.
- Add loading, empty, disabled, error, and success states for user-facing flows.
- Keep common workflows ergonomic for repeated use: minimize mode switching, preserve context, and make navigation predictable.
- For complex canvases or editors, toolbars should be icon-first with tooltips for unfamiliar actions.
Verification
Before finishing frontend work:
- Run the relevant typecheck or build.
- Inspect the UI in browser screenshots when a dev server can run.
- Check at least one desktop and one mobile width for clipping, overlap, and unusable controls.
- Scan CSS color usage; revise if the page reads as a single dominant hue unless that is an explicit brand constraint.
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.
- 11d ago First seen · 59 lines · 43 tokens per session scan A 8f5c9dbbe9df
design-taste-frontend is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 496 once invoked, about $0.0002 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
frontman-dev
AI-powered visual frontend editing in your browser. Click any element in your running app, describe changes in plain English, and get real source file edits with instant hot reload. Works with Next.js, Astro, and Vite.
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
redesign-existing-projects
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.
minimalist-ui
Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.