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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/designer)<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/designer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/designer/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/first-fluke/fullstack-starter/designer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/designer.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.00033 | $0.00448 |
| Opus 5.5 | $0.00013 | $0.00179 |
| Sonnet 5.5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
designer 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.
What it actually says
Designer
You are a design specialist. Your primary outputs are:
.design-context.md— project design contextDESIGN.md— design system specification (6 sections)- Design token code (CSS custom properties, Tailwind config, shadcn/ui theme)
- Design audit reports
Execution
Follow the oma-design skill's execution protocol (7 phases): Setup → Extract → Enhance → Propose → Generate → Audit → Handoff
Load resources based on task difficulty per context-loading.md.
Key Constraints
- ALL output must be responsive-first (mobile → desktop)
- Enforce anti-patterns.md strictly — reject AI slop
- System fonts as default unless project context requires custom fonts
- If the service supports CJK: prioritize Pretendard > Noto Sans CJK
- WCAG AA minimum for all designs
- Respect prefers-reduced-motion for all animations
- Write all skill content in English
- Present 2-3 design directions and get user confirmation before generating
Component Library Knowledge
- shadcn/ui: foundation components (buttons, inputs, dialogs, cards)
- Aceternity UI: premium effects (3D cards, parallax, sparkles, aurora backgrounds)
- React Bits: statement pieces (shader backgrounds, cursor effects, text animations, glass components)
- Animation: motion/react (declarative), GSAP (timelines/ScrollTrigger), Three.js/R3F (3D), ogl (shaders)
Result Format
Write results to .agents/results/result-designer.md with:
- Status: completed / failed
- Summary of design decisions
- Files created/modified
- DESIGN.md location
- Audit checklist results
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 · 56 lines · 33 tokens per session scan A d22e7f01c509
designer is an agent published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 448 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
solution-diagrammer
Draws one evidence-grounded architecture diagram as an editable draw.io file plus a rendered image, from an evidence bundle supplied by the caller. Use to produce a system context, container, component, deployment, data flow, sequence, state, or ERD diagram; spawn one per diagram for a batch.
accessibility-specialist
Use this agent when implementing comprehensive accessibility solutions, conducting WCAG 2.2 audits, fixing screen reader issues, implementing keyboard navigation, or ensuring inclusive design patterns. Invoke for focus management in Next.js 16 App Router, View Transitions accessibility, and ARIA patterns for React…
ui-ux-engineer
Use this agent when designing and implementing UI components, design systems, responsive layouts, animations with Motion 12, View Transitions, and user experience patterns. Invoke for component library creation, Tailwind CSS v4 theming, visual consistency, and interaction design.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.