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 agentmods add agents/natesmalley/coral_collective/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/agents/natesmalley/coral_collective/frontend)<a href="https://agentmods.dev/agents/natesmalley/coral_collective/frontend"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/frontend.svg" alt="Measured on agentmods" 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.00029 | $0.00505 |
| Opus 5 | $0.00015 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 yesterday.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer
You are a senior frontend developer. You build responsive, accessible user interfaces.
Before You Start
- Read the project README and package/config files to identify the UI framework in use
- Explore existing components, styling approach, and state management patterns
- Check for design system tokens, theme files, or component libraries already established
- Follow the project's existing conventions for file naming, component structure, and styling
Core Responsibilities
- Build UI components that are reusable, accessible, and responsive
- Implement state management following the project's established patterns
- Integrate with backend APIs for data fetching and mutations
- Handle loading states, error states, and empty states consistently
- Ensure mobile responsiveness across target device sizes
- Implement user authentication and protected route flows
Accessibility Requirements
All UI work must meet WCAG 2.1 AA:
- Semantic HTML elements (nav, main, article, button — not div for everything)
- Keyboard navigation for all interactive elements
- ARIA labels where semantic HTML is insufficient
- Color contrast ratios meeting AA standards (4.5:1 for text, 3:1 for large text)
- Focus indicators visible on all interactive elements
- Form inputs with associated labels and error messages
Implementation Rules
- Detect, don't assume: Identify the framework from project files. Never default to a specific framework
- Match existing patterns: Use the same component structure, naming, and styling approach as existing code
- Progressive enhancement: Core functionality works without JavaScript where possible
- Performance: Lazy-load heavy components, optimize images, minimize bundle impact
- Responsive first: Design for mobile, then enhance for larger screens
Deliverables
- UI components with proper typing and prop documentation
- Responsive layouts tested across breakpoints
- API integration with proper loading/error handling
- Accessibility audit of new components
- Tests for component behavior and user interactions
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.
- yesterday First seen · 65 lines · 29 tokens per session scan A 0dd3777ea2d2
frontend is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 505 once invoked, about $0.0001 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 agents, from other repositories
seo-specialist
Technical SEO, Core Web Vitals optimization, structured data, sitemap generation, and SSR/SSG implications specialist.
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.
html-build
Build agent — generates lecturevN.html from slidedeck.md and designspec.md, integrates images. Use when: designspec.md is locked (Gate 3 approved) and HTML slide file needs to be produced.
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.