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 roedyrustam/vibes-plug --skill senior-frontendgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/senior-frontend)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/senior-frontend"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/senior-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/roedyrustam/vibes-plug/senior-frontend"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/senior-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01959 |
| Opus 5 | $0.00025 | $0.00979 |
| Sonnet 5 | $0.00010 | $0.00392 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
senior-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 6d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Frontend Specialist (2026 Edition)
English
Description
Production-grade frontend development patterns, performance optimization, and modern ecosystem integrations for React 19 / Next.js 15 applications with Tailwind CSS v4 and TypeScript. Covers React 19 Compiler, Partial Prerendering (PPR), View Transitions API, and SPA/MPA hybrid strategies.
Orchestration & Integration
ui-components-expert: For building robust UI components (Radix, shadcn).tailwind-expert: For styling and custom @theme configurations.nextjs-app-router-expert: For RSC, caching, and Next.js routing patterns.state-management-expert: For client-side state (Zustand, Jotai).tanstack-query-expert: For advanced data fetching and server state caching.spa-orchestrator: For Single-Page Application architectures.mpa-orchestrator: For Multi-Page Application architectures.
Trigger Conditions
- Scaffold a new React or Next.js 15 project with TypeScript and Tailwind CSS v4.
- Generate new components, custom hooks, or Server Actions.
- Analyze and optimize bundle sizes and Core Web Vitals.
- Implement advanced React 19 patterns (
useActionState,useOptimistic,use()). - Build SPAs — coordinate with
spa-orchestrator. - Ensure accessibility compliance (WCAG 2.2) and testing.
Technical Guidelines & Best Practices
1. Next.js 15: Server vs Client Components
Use Server Components by default for performance and SEO. Use 'use client' strictly for:
- State (
useState,useEffect), event handlers (onClick), browser APIs. - Interactive UI needing client hydration.
Next.js 15.2+ Requirements:
- Await
Promise-basedparamsandsearchParamsbefore accessing properties. - Use Partial Prerendering (PPR) natively. Wrap dynamic sections in
<Suspense>.
2. React 19 Compiler & Hooks
Do not use useMemo, useCallback, or React.memo unless explicitly required; rely on the React 19 compiler.
What ships with it
6 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.
- 6d ago First seen · 142 lines · 50 tokens per session scan A d918e2e1532e
senior-frontend is a skill published in the GitHub repository roedyrustam/vibes-plug (50 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,959 once invoked, about $0.0003 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-03.
Other skills, from other repositories
nextjs-react-typescript
A coding guide for TypeScript applications built with React and Next.js, using common interface and styling tools.
typescript-style
Validate TypeScript/React code against style and architectural conventions.
expo-app-design
Build beautiful cross-platform mobile apps with Expo Router, NativeWind, and React Native.
react-best-practices
React development guidelines with hooks, component patterns, state management, and performance optimization.
upgrading-expo
Guidelines for upgrading Expo SDK versions and fixing dependency issues.
react-component-development
Component patterns and best practices for React with TypeScript. Covers functional components, custom hooks, state management, composition patterns, error boundaries, server components, and form handling. Keywords: React component, hooks, state management, TypeScript component, custom hooks, Zustand, useReducer…