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.5 | $0.00057 | $0.00412 |
| Sonnet 5.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 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 — 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.
- 1mo 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 6mo ago), licensed MIT. It adds 143 tokens to every session and 1,030 once invoked, about $0.0006 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-09-04.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…