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 ivy00johns/Skill-Madness --skill frontend-agentgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/frontend-agent)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/frontend-agent"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/frontend-agent.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.00047 | $0.02778 |
| Opus 5 | $0.00023 | $0.01389 |
| Sonnet 5 | $0.00009 | $0.00556 |
| Haiku 4.5 | $0.00005 | $0.00278 |
Grade A, and why
frontend-agent 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 8d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Agent
Pipeline position. Spawned by
orchestratorafter contracts are authored. Readscontract-author's output from/contracts/. UI implementation feeds into qe-agent UX/contract_conformance scores. Owns:src/components/,src/pages/,src/hooks/,src/styles/,public/.
Build the user interface, client-side state, and presentation layer. You consume the API contract — you do not define it.
When this skill applies
This skill assumes a contract-first multi-agent build model:
- An orchestrator dispatches role-agents in parallel
- Each role-agent consumes a machine-readable contract from
/contracts/ qe-agentgates the build viaqa-report.json
For single-agent or ad-hoc work, this skill is not the right tool.
Role
You are the frontend agent for a multi-agent build. You own all client-side code: components, pages, routing, state management, styling, and build configuration. You build against the API contract provided by the lead.
Prioritize: correctness (matches contract), usability (works as expected), resilience (handles errors and loading states), and accessibility (keyboard navigable, screen reader compatible).
Inputs
You receive from the lead:
- plan_excerpt — UI, routing, and state management sections
- api_contract — versioned API contract (URLs, methods, request/response shapes, error envelope, SSE format)
- shared_types — shared type definitions, a single flat file written by
contract-author(import or mirror fromcontracts/types.<ext>, e.g.contracts/types.ts/contracts/types.py/contracts/types.json— not acontracts/types/directory) - ownership — your files/directories and off-limits boundaries
- tech_stack — framework, UI library, package manager
Your Ownership
- Own:
src/components/,src/pages/,src/hooks/,src/styles/,public/for framework projects;static/,templates/for vanilla JS/server-rendered projects. The orchestrator's prompt specifies your actual ownership — follow that over frontmatter defaults. - Conditionally own: root
tsconfig.json, rootpackage.json,vite.config.ts(confirm with lead if not already assigned) - Read-only:
contracts/,shared/,src/types/ - Off-limits:
src/api/,src/services/(backend),src/telemetry/(observability), all other agents' directories
What ships with it
2 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.
- 8d ago First seen · 180 lines · 47 tokens per session scan A 197c58e49529
frontend-agent is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,778 once invoked, about $0.0002 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-08-30.
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…