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 aegntic/compound-engineering --skill frontend-designgit clone --depth 1 https://github.com/aegntic/compound-engineeringWrote 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/aegntic/compound-engineering/frontend-design)<a href="https://agentmods.dev/skills/aegntic/compound-engineering/frontend-design"><img src="https://agentmods.dev/badge/skills/aegntic/compound-engineering/frontend-design/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/aegntic/compound-engineering/frontend-design"><img src="https://agentmods.dev/badge/skills/aegntic/compound-engineering/frontend-design.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.00048 | $0.01520 |
| Opus 5.5 | $0.00019 | $0.00608 |
| Sonnet 5.5 | $0.00010 | $0.00304 |
| Haiku 4.5 | $0.00005 | $0.00152 |
Grade A, and why
frontend-design 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 1mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
Design Thinking
Before coding, understand the context and commit to a BOLD aesthetic direction:
- Purpose: What problem does this interface solve? Who uses it?
- Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
- Constraints: Technical requirements (framework, performance, accessibility).
- Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?
CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work -- the key is intentionality, not intensity.
Framework-Specific Patterns
Adapt to the project's framework. Detect and follow existing conventions:
React / Next.js:
- Functional components with hooks
- CSS Modules, Tailwind CSS, or styled-components (match project convention)
- Use
motion(Framer Motion) for animations when available - Component composition over inheritance
Vue 3 / Nuxt 3:
- Composition API with
<script setup> - Scoped styles with
<style scoped> - Composables for shared logic
defineProps/defineEmitsfor component contracts
Angular:
- Standalone components (Angular 17+)
- Signal-based reactivity where supported
- OnPush change detection strategy
- Angular CDK for accessible primitives
Svelte / SvelteKit:
- Reactive declarations with
$: - Svelte transitions and animations
- Component slots for composition
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.
- 1mo ago First seen · 116 lines · 48 tokens per session scan A 95df0ed26d96
frontend-design is a skill published in the GitHub repository aegntic/compound-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,520 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
stitch-cli
Drives Google Stitch (stitch.withgoogle.com), the AI UI design tool, via the cli-web-stitch command-line tool — create design projects from text prompts, iterate on designs with AI (flash/pro/redesign models), manage projects (rename, duplicate, delete, download), and view or download generated screen HTML. Use when…
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.
river-review-architecture
An architecture-review guide that checks whether software design decisions, system boundaries, and data models fit together consistently. An architecture review examines the structure and dependencies of a system.
Component Variants / States Documentation コンポーネント状態の文書化
A code review check for new reusable interface components and the variations and states they support, such as hover, focus, disabled, loading, and error states.
Design Source-of-Truth Conformance デザイン定義準拠
A code review check that compares new interface values—such as colors, spacing, font sizes, rounded corners, and shadows—with the project's documented design rules or token files. It only runs when those design definitions exist.
Pre-mortem 失敗シナリオ分析
A review skill that imagines a future serious failure and works backward to find how it could happen. This approach is called a pre-mortem.