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 skills/rajanchavada/rosetta/frontend-react-nextnpx skills add RajanChavada/Rosetta --skill frontend-react-nextgit clone --depth 1 https://github.com/RajanChavada/RosettaWrote 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/rajanchavada/rosetta/frontend-react-next)<a href="https://agentmods.dev/skills/rajanchavada/rosetta/frontend-react-next"><img src="https://agentmods.dev/badge/skills/rajanchavada/rosetta/frontend-react-next.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 | $0.00026 | $0.00441 |
| Opus 5 | $0.00013 | $0.00220 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
frontend-react-next 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.
What it actually says
Frontend: React/Next.js Skill
Expert Intent
Implement high-fidelity, high-performance user interfaces. This skill enforces component modularity, strict prop-types/TS safety, and optimized rendering strategies (Server vs Client components) to ensure a premium user experience in Rosetta.
Pre-Checks & Context Intake
- Design System Audit: Scan for existing components, tailwind configs, or global styles.
- Routing State: Identify the use of App Router vs Pages Router.
- Context/State: Locate the primary state management solution (Zustand, Redux, Context API).
- Core Stack: follow patterns for Svelte, Native mobile.
- Constraint check: Read
AGENT.mdfor accessibility and performance requirements.
Expert Workflow (SOF)
- Atomic Design: Break the UI down into Atoms, Molecules, and Organisms.
- Requirement: Design for reuse and clear PROP contracts.
- State Strategy: Decide between Server-side fetching (RSC) and Client-side state hooks.
- Implementation: Code with a focus on semantic HTML and accessibility (A11y).
- Optimization: Audit for unnecessary re-renders (useMemo, useCallback) and Core Web Vitals (LCP, CLS).
- Verification: Run snapshot or component tests for critical UI paths.
Strict Guardrails
- PROPS: strictly forbid "Prop Drilling" beyond 3 levels. Use Context or State Management instead.
- PERFORMANCE: No large (>50kb) third-party libraries without explicit architecture review.
- A11Y: Do not commit components that fail basic screen-reader or contrast checks.
Expected Output
- Modular, well-documented React/Next.js components.
- Integrated API fetching logic with error boundaries.
- Component/Snapshot tests for new UI logic.
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 · 38 lines · 26 tokens per session scan A 158f63aa6c19
frontend-react-next is a skill published in the GitHub repository RajanChavada/Rosetta (3 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 441 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-08-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.