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 frontendgit 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)<a href="https://agentmods.dev/skills/insajin/autopus-adk/frontend"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/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/insajin/autopus-adk/frontend"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/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.00058 | $0.02523 |
| Opus 5.5 | $0.00023 | $0.01009 |
| Sonnet 5.5 | $0.00012 | $0.00505 |
| Haiku 4.5 | $0.00006 | $0.00252 |
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 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.
This is a copy
97% identical to frontend-skill — 17 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 — 254 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.
- 1mo ago First seen · 254 lines · 58 tokens per session scan A af1da209b886
frontend-skill is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 2,523 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to frontend-skill, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
fast-agent-design
Use this skill to generate well-branded interfaces and assets for fast-agent, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for protoyping.
anti-slop-frontend
A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
craft-studio
Router for the ArtCraft craft apps (PhotoCraft, VectorCraft, FilmCraft, LightCraft, PdfCraft, EffectCraft, DesignCraft, FigCraft, WordCraft, SoundCraft, DeckCraft, CADCraft, GridCraft) driven headless via pi-craft. Use to choose which app fits a job and run the discover-execute-save-verify loop - "which craft app…
brand-identity
Use when a project needs its visual foundation built or consolidated into one system: logo brief, color system in HEX/RGB/CMYK/OKLCH with proven AA contrast, type system, usage rules, and an exported W3C design-tokens.json that later skills consume. NOT the applied UI pixels (that is design), NOT the words or tone…
plan
Use when an approved, clarified spec must become a technical blueprint before any code — the SDD phase between clarify and tasks: architecture, contracts, data flow, testing strategy, sequencing and risks, at structure altitude, never framework syntax. NOT the what/why spec (that is specify), NOT the ambiguity sweep…