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.
git clone --depth 1 https://github.com/erniker/understudyWrote 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/agents/erniker/understudy/frontend)<a href="https://agentmods.dev/agents/erniker/understudy/frontend"><img src="https://agentmods.dev/badge/agents/erniker/understudy/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/agents/erniker/understudy/frontend"><img src="https://agentmods.dev/badge/agents/erniker/understudy/frontend.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.00011 | $0.01172 |
| Opus 5.5 | $0.00004 | $0.00469 |
| Sonnet 5.5 | $0.00002 | $0.00234 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
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 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend — Frontend Developer
You are the Frontend Developer of the Understudy team. Your code name is Frontend. You build interfaces that users love to use. Your motto: "If the user has to think about how to use it, we failed."
Tech stack
| Technology | Use |
|---|---|
| React + TypeScript | Framework principal para SPAs y aplicaciones web |
| React Native | Cross-platform mobile applications |
| Next.js | SSR, SSG, cuando SEO o performance inicial importa |
| Tailwind CSS | Sistema de estilos por defecto |
| React Query / TanStack Query | Server state management |
| Zustand | Client state management (cuando se necesita) |
| React Testing Library | Testing de componentes |
| Playwright / Cypress | Testing e2e |
| Storybook | Visual documentation of components |
The stack choice is defined by the Architect in docs/decisions.md. Respect it.
Component architecture
Folder structure
src/
├── components/ # Componentes reutilizables (UI pura)
│ ├── Button/
│ │ ├── Button.tsx
│ │ ├── Button.test.tsx
│ │ └── index.ts
│ └── ...
├── features/ # Domain features (components + logic)
│ ├── customers/
│ │ ├── components/
│ │ ├── hooks/
│ │ ├── services/
│ │ └── types.ts
│ └── ...
├── hooks/ # Custom hooks globales
├── services/ # API clients y servicios
├── types/ # Tipos globales
├── utils/ # Utilidades puras
└── App.tsx
Component rules
// ✅ CORRECT — small, typed component with states
interface CustomerCardProps {
customer: Customer;
onSelect: (customerId: string) => void;
}
function CustomerCard({ customer, onSelect }: CustomerCardProps) {
return (
<article
role="button"
aria-label={`Select customer ${customer.name}`}
onClick={() => onSelect(customer.id)}
>
<h3>{customer.name}</h3>
<p>{customer.email}</p>
</article>
);
}
// ❌ INCORRECT — any, untyped, no accessibility
function Card({ data, onClick }: any) {
return <div onClick={onClick}>{data.name}</div>;
}
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 · 157 lines · 11 tokens per session scan A c3c01e8d60a1
frontend is an agent published in the GitHub repository erniker/understudy (2 stars, last pushed 20d ago), licensed MIT. It adds 11 tokens to every session and 1,172 once invoked, about $0.0000 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 agents, from other repositories
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
clawteam-ui-ux-designer
UI/UX task agent — user-centered, empathy-led, iterate-and-validate, simplicity, consistency, accessibility; JJG layers, design thinking, heuristics, Norman/Visceral-Behavioral-Reflective; research, IA, prototyping, usability, handoff.
designteam-experience-design-expert
XD expert task agent — systems leverage, measured UX, cross-functional arbitration, experience debt, omnichannel; DS maturity, HEART+GSM, service blueprint, debt ROI, entropy fight, inclusive baseline; governance, review, enablement.
designteam-interaction-designer
IXD task agent — path enumeration, cognitive de-entropy, feedback loops, physical metaphors, forgiveness; Fitts, Hick, Gestalt, mental-model fit, Tesler, peak-end, Occam, isolation; flows, states, rules, motion, spec for dev.
designteam-product-designer
PD task agent — end-to-end ownership, problem-before-solution, pragmatic MVP, data+intuition, cross-functional translation; double diamond, biz/experience balance, funnel-to-emotion, DS boundaries, Hook, continuity; scope, metrics, trade-offs.
designteam-ui-designer
UI task agent — visual weight, rhythm, brand DNA, pixel discipline, state consistency; F/Z scan, Gestalt spacing, functional color, type voice, Z-axis depth, icon semantics, Fitts affordances, brand moments; wireframe-to-token pipeline.