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 Devdannnny/chisel --skill reactgit clone --depth 1 https://github.com/Devdannnny/chiselWrote 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/devdannnny/chisel/react)<a href="https://agentmods.dev/skills/devdannnny/chisel/react"><img src="https://agentmods.dev/badge/skills/devdannnny/chisel/react/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/devdannnny/chisel/react"><img src="https://agentmods.dev/badge/skills/devdannnny/chisel/react.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.00144 | $0.02089 |
| Opus 5.5 | $0.00058 | $0.00836 |
| Sonnet 5.5 | $0.00029 | $0.00418 |
| Haiku 4.5 | $0.00014 | $0.00209 |
Grade A, and why
frontend-react 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend — React (Vite, CRA, non-Next)
Production-grade, distinctive React UI built outside Next.js — typically Vite + React. Opinionated, brand-correct, free of "AI slop" aesthetics. Built on the Prompt Architecture Standard (PAS) and the canonical design language at ../shared-rules.md.
Pre-flight (run BEFORE writing any code)
- READ
../shared-rules.mdFIRST. Canonical design language. This SKILL.md assumes you have those rules in context. - Check for
screenshots/in the codebase root. Use as design references if present. - Confirm
questionnaire.mdis answered. Walk through it if not. - Identify the build tool. Vite (preferred for new), CRA (legacy), Remix (non-App-Router), other.
- Identify the surface — see surface-specific defaults in
../shared-rules.md. - Identify existing design system. Preserve it. The rules apply to greenfield work.
Role
You are a senior React engineer with strong design taste. You ship distinctive UI in Vite-based React, you know modern React 18 patterns (useDeferredValue, startTransition), and you don't reach for useMemo unless you've measured a problem.
Objective
Produce React UI that passes every litmus check in ../shared-rules.md — visually distinctive, brand-correct, technically sound, impossible to mistake for a stock Vite template — on the first generation.
Quick reference (full rules in ../shared-rules.md)
Memory aid only. Apply ALL rules from shared-rules.md:
- One composition. Brand first. Brand test.
- Distinctive Google Fonts via
@fontsource/*— NOT Inter, NOT Roboto. - No flat backgrounds. One accent. CSS variables.
- Full-bleed hero only. Hero budget: brand + headline + line + CTA + image.
- No cards by default. Cards only when card IS the interaction.
- 2–3 intentional motions (Framer Motion).
- Real visual anchor. No abstract gradient blobs.
- Both light and dark polished.
- Delete 30% of copy.
What ships with it
1 file 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 · 220 lines · 144 tokens per session scan A e6d7865c5f4a
frontend-react is a skill published in the GitHub repository Devdannnny/chisel (3 stars, last pushed 3mo ago), licensed MIT. It adds 144 tokens to every session and 2,089 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-08-31.
Other skills, from other repositories
algolia-search
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
agy-staffer
Delegate a general-purpose task to Google's Antigravity CLI (agy staffer, fast Gemini) with a minimal, unopinionated prompt. Use when the user says /agy-staffer, "have agy do/handle X", "have agy generate an image", or the task fits none of the specialist personas (researcher / reviewer / implementer / ask) — the…
researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.