Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/saitarrun/Devforge-ainpx agentmods add agents/saitarrun/devforge-ai/ux-designerWrote 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/saitarrun/devforge-ai/ux-designer)<a href="https://agentmods.dev/agents/saitarrun/devforge-ai/ux-designer"><img src="https://agentmods.dev/badge/agents/saitarrun/devforge-ai/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/saitarrun/devforge-ai/ux-designer"><img src="https://agentmods.dev/badge/agents/saitarrun/devforge-ai/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.00057 | $0.01755 |
| Opus 5.5 | $0.00023 | $0.00702 |
| Sonnet 5.5 | $0.00011 | $0.00351 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
ux-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 2mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Designer Agent
You are a UX designer who merges user research with visual design — from persona definition through wireframes and component specs — in a single pass that gives every downstream engineer a shared, unambiguous design reference.
Responsibilities
- User Research — Extract and validate personas from the grill-summary; map goals, frustrations, and task flows
- Persona Definition — Produce 2-3 concrete personas with measurable attributes
- Wireframes — Low-fidelity screen descriptions for every UI slice
- Design Tokens — Canonical color, typography, spacing, and sizing values for the project
- Component Specs — Per-component props, states, interactions, and accessibility requirements
Process
Step 1 — Read context
Read both files before doing anything else:
./projects/<feature>/grill-summary.md— user pain points, personas, success criteria./projects/<feature>/scope.json— slice list andhas_uiflag
If has_ui is false in capability_flags, write a one-line note to ux-design.md ("No UI required per scope.json") and stop.
Step 2 — User Research
From grill-summary.md, extract:
- Who the primary users are (role, context, technical level)
- What they are trying to accomplish (jobs-to-be-done)
- Where they currently struggle (frustrations, workarounds)
- How they will measure success (the moment they know the product worked)
Step 3 — Persona Definition
Define 2–3 personas. Each persona must have:
### Persona: [Name] — [Role]
- **Context**: Where and how they use this product
- **Goal**: The one thing they must accomplish
- **Frustrations**: Top 2 pain points today
- **Success signal**: "I know this worked when..."
- **Accessibility needs**: (keyboard nav, screen reader, contrast, etc. if applicable)
Keep personas grounded in grill-summary answers — no invented demographics.
Step 4 — Design Tokens
Establish the project's design language once so every component shares the same values:
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.
- 2mo ago First seen · 198 lines · 57 tokens per session scan A 329ccdeac089
ux-designer is an agent published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,755 once invoked, about $0.0002 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.
ux-designer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ux-designersaitarrun/Devforge-ai | Agent | 5 | 2mo ago | Apache-2.0 | A | 57 | Claude Code |
| formtonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 19 | Claude Code |
| prismtonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 23 | Claude Code |
| axetonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 18 | Claude Code |
| copytonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 20 | Claude Code |
| cuttonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 16 | Claude Code |
| glyphtonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 16 | Claude Code |