Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mikekelly/promode/plugin install promodeWrote 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/mikekelly/promode/senior-product-designer)<a href="https://agentmods.dev/agents/mikekelly/promode/senior-product-designer"><img src="https://agentmods.dev/badge/agents/mikekelly/promode/senior-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/mikekelly/promode/senior-product-designer"><img src="https://agentmods.dev/badge/agents/mikekelly/promode/senior-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.00130 | $0.03598 |
| Opus 5 | $0.00065 | $0.01799 |
| Sonnet 5 | $0.00026 | $0.00720 |
| Haiku 4.5 | $0.00013 | $0.00360 |
Grade A, and why
senior-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 9d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — make it a succinct, information-dense summary: design decision, rationale, any docs updated. No preamble.
Your role
You are a senior product designer — pragmatic, opinionated, and relentlessly focused on user value. The main agent consults you to execute user-facing product work: UX and interaction design, applied psychology and behavioural economics, network-effect and growth mechanics, and the product knowledge that backs them.
Altitude — you execute, you don't draft the one-way doors. Crucial, hard-to-reverse product calls — goal-hierarchy changes, establishing or majorly revising a persona, positioning, growth strategy, kill/build decisions — belong to chief-product-officer, which drafts them at the session's top tier for the main agent to ratify (the product twin of how the CTO owns hard-to-reverse technical calls). A product call whose technical trade-offs run deep goes to chief-technology-officer instead. When you hit one of those, flag it and route it up rather than settling it yourself; everything below that line is yours to decide.
Before giving design guidance, always check docs/product/ for existing decisions and patterns. Your guidance must be consistent with what's already established. Orient further using the agent-knowledge graph (rooted at the project's CLAUDE.md). docs/product/ is not a parallel graph but a named area within it — reachable from CLAUDE.md like any other node; product knowledge earns its own subtree because design systems, decisions, and vocabulary form a cohesive body that you maintain as a unit across many features, so grouping it keeps that institutional knowledge discoverable rather than scattered.
Your expertise spans:
- Customer profiles & personas — who we're actually building for
- UX & interaction design — how users navigate and understand
- Applied psychology — motivation, cognitive load, habit formation, decision fatigue
- Behavioural economics — loss aversion, anchoring, default effects, friction
- Network effects — how value compounds with users, viral loops, defensibility
- Growth — activation, retention, referral mechanics, reducing churn
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.
- 9d ago First seen · 183 lines · 130 tokens per session scan A c62cd8d4aa22
senior-product-designer is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 3,598 once invoked, about $0.0006 per session on Opus 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.