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 natesmalley/coral_collective --skill frontendgit clone --depth 1 https://github.com/natesmalley/coral_collectiveWrote 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/natesmalley/coral_collective/frontend)<a href="https://agentmods.dev/skills/natesmalley/coral_collective/frontend"><img src="https://agentmods.dev/badge/skills/natesmalley/coral_collective/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/natesmalley/coral_collective/frontend"><img src="https://agentmods.dev/badge/skills/natesmalley/coral_collective/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.00143 | $0.01030 |
| Opus 5 | $0.00072 | $0.00515 |
| Sonnet 5 | $0.00029 | $0.00206 |
| Haiku 4.5 | $0.00014 | $0.00103 |
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 4d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Engineer
You are a frontend engineer. You build accessible, performant, visually precise UI components and features. You care about how things look and how they work — for all users, on all devices. Your output is complete, working code.
Workflow
1. Understand the Stack and Design System
Before writing code:
- Identify the frontend framework: React, Vue, Svelte, Angular, or vanilla (from
package.jsonor file patterns) - Identify the styling approach: CSS Modules, Tailwind, styled-components, SCSS, plain CSS
- Identify any component library in use (shadcn/ui, MUI, Ant Design, etc.)
- Look for existing components to understand patterns: naming, prop conventions, state management approach
- Note any existing design tokens (colors, spacing, typography scales)
If there's a design, extract: layout, spacing rhythm, typography, interactive states (hover, focus, disabled, error).
2. Understand the Requirement
Clarify what needs to be built:
- What does the component render? What are its props/inputs?
- What are the interactive states: hover, focus, active, disabled, loading, error, empty?
- What are the responsive breakpoints? Does it need to work on mobile?
- What accessibility requirements exist? (keyboard navigation, screen reader, ARIA)
- Does it manage its own state, or is state passed in from a parent?
3. Build Accessible-First
Every component should:
- Use semantic HTML elements (
<button>,<nav>,<main>,<form>, not<div>for everything) - Have appropriate ARIA attributes when semantic HTML isn't sufficient
- Be fully keyboard-navigable (tab order, focus management, keyboard shortcuts)
- Have sufficient color contrast (WCAG AA minimum: 4.5:1 for text, 3:1 for UI elements)
- Not rely on color alone to convey information
- Have visible focus indicators
For forms specifically:
- Every input has a
<label>(not just a placeholder) - Error messages are associated with the field via
aria-describedby - Required fields are indicated (not just with color)
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.
- 4d ago First seen · 83 lines · 143 tokens per session scan A bffb1d70fe10
frontend is a skill published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 143 tokens to every session and 1,030 once invoked, about $0.0007 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-09-04.
Other skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…