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 Insajin/autopus-adk --skill frontend-skillgit clone --depth 1 https://github.com/Insajin/autopus-adkWrote 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/insajin/autopus-adk/frontend-skill)<a href="https://agentmods.dev/skills/insajin/autopus-adk/frontend-skill"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/frontend-skill/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/insajin/autopus-adk/frontend-skill"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/frontend-skill.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.00058 | $0.02423 |
| Opus 5 | $0.00029 | $0.01211 |
| Sonnet 5 | $0.00012 | $0.00485 |
| Haiku 4.5 | $0.00006 | $0.00242 |
Grade A, and why
frontend-skill 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.
This is a copy
81% identical to frontend-skill — 56 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend skill
Use this skill when the quality of the work depends on art direction, hierarchy, restraint, imagery, and motion rather than component count.
Goal: ship interfaces that feel deliberate, premium, and current. Default toward award-level composition: one big idea, strong imagery, sparse copy, rigorous spacing, and a small number of memorable motions.
Working Model
Before building, write three things:
- visual thesis: one sentence describing mood, material, and energy
- content plan: hero, support, detail, final CTA
- interaction thesis: 2-3 motion ideas that change the feel of the page
Each section gets one job, one dominant visual idea, and one primary takeaway or action.
UX Intelligence Pass
Run this pass before choosing components, colors, or layout. It is a compact design-system generator inspired by professional UI/UX skill packs, but it must use this project's existing design sources and stack conventions first.
Create a short Design Discovery Matrix:
| Dimension | Decision |
|---|---|
| Surface type | marketing page / app workspace / dashboard / editor / mobile flow / game / docs |
| Product category | SaaS, finance, healthcare, marketplace, devtool, media, commerce, civic, lifestyle, etc. |
| Primary user | who uses it, how often, and under what pressure |
| Core job | the task the first screen must make easier |
| Density | sparse, balanced, operational, data-dense |
| Trust and risk | low, medium, high; note money, health, security, production-change, or destructive-action risk |
| Platform stack | web, mobile, desktop, responsive web, 3D/game, native shell |
Then synthesize the working design system:
- page or screen pattern: hero-centric, trust/authority, interactive demo, data-dense dashboard, editor workspace, wizard, gallery, marketplace, or operational console
- style posture: restrained/minimal, editorial, premium, playful, technical, accessible/public-service, immersive, or brand-led
- palette roles: primary, accent, surface, muted, danger, success, focus, and data colors; prefer semantic tokens over raw hex in components
- typography: heading/body roles, scale, line height, data/table number treatment, and whether display type is allowed
- components: required primitives, empty/loading/error/disabled states, icon set, card usage, form pattern, nav pattern
- motion: what motion communicates, duration range, reduced-motion fallback, and what must stay static
- anti-patterns: styles that would damage trust, readability, performance, or product fit
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 First seen · 239 lines · 58 tokens per session scan A 415dc96bf41a
frontend-skill is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 2,423 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to frontend-skill, differing in 56 lines, and is treated as a copy.
Other skills, from other repositories
css-architecture
CSS architecture, design token strategy, Tailwind conventions, CSS Modules, container queries, dark mode, responsive patterns, and animation architecture. Use for design token naming, CSS custom properties, Tailwind config, container queries, dark mode implementation, fluid typography, or CSS animation decisions.…
design-system-tokens
Token architecture and component specifications. Three-layer tokens (primitive → semantic → component), CSS variables, spacing/typography scales, and component state definitions. Use for design token creation and systematic design.
design-md
Google's open DESIGN.md specification for describing visual identities to coding agents. YAML tokens + Markdown rationale + npx CLI for WCAG validation and W3C DTCG/Tailwind export. Use for formal, agent-consumable design system documentation.
popular-web-designs
54 real-world design systems (Stripe, Linear, Vercel, Supabase, Apple, Notion, Cursor, etc.) as ready-to-use HTML/CSS reference. Exact color palettes, typography hierarchies, component specs, spacing, shadow systems, and font substitutions. Use when building UI that should match a specific company's aesthetic.
artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
warm-editorial-ui
Apply the "Warm Editorial Refinement" design system — a sophisticated, executive-grade aesthetic with warm cream surfaces (light mode) and warm charcoal surfaces (dark mode), Bahnschrift + Plus Jakarta Sans typography, generous rounded corners, multi-layer shadows, and a warm neutral palette. Supports both light and…