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 telagod/code-abyss --skill frontendgit clone --depth 1 https://github.com/telagod/code-abyssWrote 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/telagod/code-abyss/frontend)<a href="https://agentmods.dev/skills/telagod/code-abyss/frontend"><img src="https://agentmods.dev/badge/skills/telagod/code-abyss/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/telagod/code-abyss/frontend"><img src="https://agentmods.dev/badge/skills/telagod/code-abyss/frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.00470 |
| Opus 5.5 | $0.00032 | $0.00188 |
| Sonnet 5.5 | $0.00016 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
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 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.
What it actually says
Frontend — taste, styles, craft, and what to refuse
Rule content lives in the five files below; this SKILL.md only routes (duplicating rule
text here is drift — doctrine/04-maintenance.md governs edits to this bundle too).
Route by moment
| You are about to… | Read (in this folder) |
|---|---|
| Start any page/component/artifact — brief to shipped | process.md first; it routes onward |
| Pick a visual direction, or choose between styles | styles.md |
| Understand what makes a design striking vs mediocre; make a boring design memorable | taste.md |
| Write actual CSS values — type, space, color, depth, motion, dark mode | craft.md |
| Judge a design (yours or anyone's); name precisely why something feels cheap | garbage.md |
Start with the ONE file that matches and follow its cross-references — they are required
inputs, not optional reading. Starting from scratch usually means process.md + the two
files it points you to.
Scope and neighbors
This bundle is the visual/aesthetic layer only. Server-side design (stack, APIs,
data) → the backend bundle; whether to delegate → doctrine; how to think → methods. If the environment provides an artifact-design skill
(harness-side), it calibrates how much to invest per request; THIS bundle governs
direction and craft once you're building.
The stance
Left unguided, every model produces the same page (garbage.md §A names it precisely).
What taste means here — and why a clean-but-forgettable page counts as a failure — is
taste.md's opening; read it before judging any design.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 38 lines · 80 tokens per session scan A fb67f7347d8c
frontend is a skill published in the GitHub repository telagod/code-abyss (242 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 470 once invoked, about $0.0003 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-30.
Other skills, from other repositories
hipson-premium-ui-ux
Use for premium UI/UX review and implementation planning in Hipson frontend projects, especially screenshot-backed landing pages, forms, visual polish, accessibility, responsive behavior, and design-agent packets.
react-shadcn
Builds UI components for a React SPA (Vite) with shadcn/ui (CLI 4.21.0) and Tailwind CSS v4 on whichever component base the project uses — Base UI (default for new projects since July 2026), Radix UI (unified radix-ui package, fully supported) or React Aria (added July 2026): forms (Field/FieldLabel/FieldError pattern…
shadcn-registries
Use when configuring shadcn/ui registries (namespaced, GitHub, dynamic), components.json, presets, or any shadcn CLI command (init, add, apply, preset, view, search, docs, info, migrate, eject, build, registry).
shadcn-theming
Use when defining or auditing shadcn/ui design tokens, OKLCH colors, or dark/light mode CSS variables.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
web-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.