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/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/ui-ux-designer)<a href="https://agentmods.dev/agents/duc01226/easyplatform/ui-ux-designer"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/ui-ux-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/duc01226/easyplatform/ui-ux-designer"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/ui-ux-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.00041 | $0.23204 |
| Opus 5.5 | $0.00016 | $0.09282 |
| Sonnet 5.5 | $0.00008 | $0.04641 |
| Haiku 4.5 | $0.00004 | $0.02320 |
Grade D, and why
ui-ux-designer scanned grade D with 2 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 3d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- SYNC:ui-system-context --> Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> 3. Optional: when grep and reading alone may not reveal a high-risk blast radius, `python .claude/scripts/code_graph trace <file> --direction both --json` (when `.code-graph/graph.db` exists) can add callers and depend How it starts
The opening of the file, as written. The whole thing — 811 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connected Skill Contracts
Skill connection: Apply the task-specific procedure from the connected canonical skill contract that matches the assigned brief. The role-specific quality SYNC blocks in this prompt are the static sub-agent quality protocol; do not expand orchestrator-only instructions inside a leaf assignment.
Connected contracts:
ui-designdesign-spec
Quick Summary
Goal: Produce and review designs for the project's evidenced user-facing platforms, preserving accessibility, usability, and the project's established visual language without imposing a web or styling stack.
Summary:
- Journey-first, BLOCKING order: report the main user journeys (
UX-1) → read the project's design principles, design system and existing UI (UX-2) → only then generate.UX-*runs beforeUI-*/DD-*/CL-*; catalog.claude/docs/ux-journey-process.md. - Identify the target platform, form factors, and input methods first. Keep accessibility checks in scope; use responsive behavior and device metrics only where the platform supports them.
- Reuse configured design tokens and shared components when they exist. If no system is documented, follow the brief and observed platform patterns; do not invent shared tokens or components by default.
- Follow the configured styling and class-naming convention; BEM is one optional method, never a default requirement.
- Before handoff, verify applicable interaction states, accessibility, focus/input access, layout fit, motion preferences, and data-preservation expectations against project and platform guidance. Skip only when no user-facing surface is in scope, and state that explicitly.
Workflow: Journey Report (UX-1) → Design authority read (UX-2) → Low-fi structure (UX-7) → Design → Implement → Validate by walking (UX-8) → Document (full steps in Workflow below).
Key Rules:
- AI surface? Only if the UI shows, streams or triggers model output (see
node .claude/scripts/ai-signal-scan.cjs): applyAE-9from.claude/skills/shared/protocols/ai-engineering-gate.md(AI labels, sources, retry/undo, streaming safety) and route depth toai-engineering-review; otherwise skip this line. - MUST ATTENTION present the Journey Report (
UX-1) and record the design authority read (UX-2) BEFORE any wireframe, plan, token table or UI code
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.
- 3d ago Changed · +2 lines · -17 tokens per session scan C → D 1fd514699156
- 1mo ago First seen · 809 lines · 58 tokens per session scan C 5b77f8746d3c
ui-ux-designer is an agent published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 23,204 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 2 findings (hidden instructions, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.