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/mtnyilmaz/agents/frontend-developernpx skills add mtnyilmaz/agents --skill frontend-developergit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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.00066 | $0.00873 |
| Opus 5 | $0.00033 | $0.00436 |
| Sonnet 5 | $0.00013 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
frontend-developer 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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer
Expert in building production-grade frontend applications with the project's tech stack.
Layer References
Server/client components, route groups, layouts, metadata, and data fetching are covered in
layers/framework/nextjs/. State management, accessibility, forms, i18n, and security are inlayers/concern/frontend/patterns.md. Design system and product UX (tokens, component layers, states, motion, docs) are inlayers/concern/frontend/design-system.md. This skill adds shared-package references, component/form templates, TanStack Table, and mobile guidance not found in layers.
Import Order
- React/Next.js imports
- Third-party libraries
@repo/*package imports- Local imports (components, hooks, lib, types)
Shared Packages Quick Reference
@repo/ui:Button, Checkbox, DropdownMenu, Select, Switch, RadioGroup, Progress, Heading, Tag, Input, Label, Separator, Skeleton, Card, Avatar, Badge, Form@repo/utils/hooks:useScreen(Tailwind breakpoints),useMounted(SSR safety)@repo/utils/toast:showSuccessToast, showErrorToastetc.
Component Template
import { Button } from "@repo/ui";
import { trpc } from "@/lib/trpc";
interface UserCardProps {
userId: string;
showActions?: boolean;
}
export function UserCard({ userId, showActions = false }: UserCardProps) {
const { data: user } = trpc.user.getById.useQuery({ id: userId });
if (!user) return <Skeleton />;
return (
<Card>
<CardHeader>{user.name}</CardHeader>
{showActions && <Button>Edit</Button>}
</Card>
);
}
Form Template
import { useForm } from "react-hook-form";
import { zodResolver } from "@hookform/resolvers/zod";
import { loginSchema } from "@repo/utils/validation";
import { Form, FormField, FormItem, FormLabel, FormMessage } from "@repo/ui";
export function LoginForm() {
const form = useForm({ resolver: zodResolver(loginSchema) });
const login = trpc.auth.login.useMutation();
const onSubmit = form.handleSubmit((data) => {
login.mutate(data);
});
return (
<Form {...form}>
<form onSubmit={onSubmit}>
<FormField name="email" control={form.control} render={({ field }) => (
<FormItem>
<FormLabel>Email</FormLabel>
<Input {...field} />
<FormMessage />
</FormItem>
)} />
</form>
</Form>
);
}
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.
- 2d ago First seen · 103 lines · 66 tokens per session scan A 3969ed423426
frontend-developer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 873 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-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…
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
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.
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.
wrdn-effect-promise-exit
Replace React/effect-atom mutation handlers that use promise-mode plus try/catch with promiseExit and explicit Exit handling. Use when lint or review flags try/catch around useAtomSet mutation calls, especially UI handlers that set error/busy state after a failed mutation.
assistant-ui-primitives
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive. Use when customizing chat UI components.