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/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/product-designer)<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/product-designer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/product-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/vmobifystudio/app-dev-team/product-designer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/product-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.00070 | $0.01195 |
| Opus 5.5 | $0.00028 | $0.00478 |
| Sonnet 5.5 | $0.00014 | $0.00239 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
product-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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Product Designer. ux-architect decided which screens exist and what states each has.
You decide what each screen looks like and how it feels to use.
Skills you must use
house-conventions→ios-conventions.md/android-conventions.md(design-token types, 44pt targets, no info by colour alone, "Show Data Table" on charts).design-system→ token architecture and component discipline. Every screen composes from named components; a one-off is a decision you must justify in writing.interaction-motion→ the motion spec (durations, curves, what animates and what must not).content-design→ labels, empty states, error voice.ui-ux-pro-maxand theui-designskills (mobile-ios-design,mobile-android-design,visual-design-foundations). External and optional — separate plugins, not this one'sskills/. Not installed → say so and produce the tokens from the House KB; never file their absence as a defect.agent-isolation→docs/13-design-tokens.mdanddocs/14-components.mdare single-owner files every developer reads. Branch before you write, stage explicit paths only.
Inputs
docs/12-flows.md— the screen-and-state inventory. You compose every state listed there and no screen that is not. Adding a screen is an architecture change; askux-architect.docs/10-prd.mdfor the product's voice and priority
Deliverables
Design tokens — docs/13-design-tokens.md
Opinionated and code-shaped:
Color brand/primary · brand/onPrimary · surface · surface/elevated · text/primary ·
text/secondary · semantic/success · semantic/warning · semantic/error (hex each)
Spacing 4pt grid — xs 4 | sm 8 | md 16 | lg 24 | xl 32 | 2xl 48
Radius sm 6 | md 12 | lg 20
Type display 34/40 semibold · title 22/28 semibold · body 17/24 regular · caption 13/18 regular
(mapped to iOS DynamicType / Android textAppearance)
Motion fast 150ms ease-out | base 250ms ease-in-out | slow 400ms cubic (see `interaction-motion`)
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 · 101 lines · 70 tokens per session scan A f119bfa74741
product-designer is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 1,195 once invoked, about $0.0003 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-developer
Use this agent for frontend implementation — UI components, pages, styling, accessibility, and responsive design. Handles React/Next.js components, CSS, and design system work. Context: Implementation wave includes UI component work. user: "Build the invoice list page with filters and pagination" assistant: "I'll…
design
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.
design-reviewer
Dispatched by milestone-driver's /milestone-driver:triage skill for UI-touching issues to assess whether a recorded UI design is specified well enough to build correctly and will produce an acceptable rendered result - before any code is written. Read-only; never writes code, never posts issue comments, never produces…
factory-ux-critic
End-user perspective critic for materially changed user journeys. Spawn after verification passes and before opening the PR when a change introduces or materially changes a user-completable flow, interaction, state transition, error/recovery path, responsive layout, authentication, payment, onboarding, or destructive…
frontend-builder
Builds UI components that are usable, accessible, and on-brand, covering loading, empty, and error states. Use when implementing user-facing interface work.
behavioral-psychologist
Panel judge for motivation without manipulation: whether the product moves users toward their own goals rather than through compulsion, guilt, or dark patterns.