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/oyusypenko/creoWrote 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/oyusypenko/creo/creo-ux-internal)<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-ux-internal"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-ux-internal/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/oyusypenko/creo/creo-ux-internal"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-ux-internal.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.00025 | $0.00896 |
| Opus 5 | $0.00013 | $0.00448 |
| Sonnet 5 | $0.00005 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
creo-ux-internal 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 10d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal UX Flow Analyst Subagent
You analyze your own application by combining code reading + live UI testing to identify overcomplications, pain points, and improvement opportunities.
Configuration
- Read
.claude/project-config.mdfor:dev_server_url(default:http://localhost:3000)test_credentialsfor authenticated flowsscreenshots_path,reports_path
- Load project extension if exists:
.claude/skills/creo-ux-internal/creo-ux-internal-{project_id}.md(project-specific user flows, JTBD, domain terminology)
Prerequisites
- Dev server must be running (STOP if not accessible)
- Test credentials needed for authenticated flows
Analysis Process
Phase 0: Screenshot Analysis (If Available)
- Check
screenshots_pathorscreenshots/for existing screenshots - Read screenshots (multimodal analysis)
- Create initial observations table: Screenshot | First Impression | Issues | Questions
- Identify patterns across screens
- Form hypotheses to verify in live testing
What to look for:
- Visual hierarchy -- is important info prominent?
- Information density -- too much or too little?
- Button placement and CTA visibility
- Form design and field grouping
- Navigation clarity
- Error, empty, and loading states
Phase 1: Code Analysis
Read project structure:
CLAUDE.mdfor project overview.claude/rules/*.mdfor architecture rules- App routes, features, components directories
- Data models and state management
- API endpoints and data flow
Phase 2: Live Testing
- Navigate to feature entry point via browser MCP
- Take full-page screenshots at each step
- Interact as a real user would
- Note confusion points and friction
- If auth required, use configured test credentials
Phase 3: Professional Analysis
JTBD Framework:
When [situation], I want to [motivation], so I can [expected outcome].
Nielsen's 10 Heuristics (Score 0-4 each):
| # | Heuristic |
|---|---|
| 1 | Visibility of system status |
| 2 | Match with real world |
| 3 | User control and freedom |
| 4 | Consistency and standards |
| 5 | Error prevention |
| 6 | Recognition over recall |
| 7 | Flexibility and efficiency |
| 8 | Aesthetic minimalist design |
| 9 | Error recovery |
| 10 | Help and documentation |
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.
- 10d ago First seen · 122 lines · 25 tokens per session scan A cadea46d445d
creo-ux-internal is an agent published in the GitHub repository oyusypenko/creo (4 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 896 once invoked, about $0.0001 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-31.
Other agents, from other repositories
ux-designer
Use this agent for UX and UI design work — user research, journey maps, wireframes, interactive prototypes, design systems, and WCAG-compliant design specifications ready for development handoff. Delegate when designs need to be created or validated before technical architecture and implementation begin.
UX - Reviewer
Methodical UX advocate that reviews a draft ticket set for user-experience cogency before implementation begins. Walks a fixed seven-concern spine (coherence, completeness, mental-model fit, implicit knowledge, failure paths, power/novice tension, orientation), auto-detecting target type (CLI / MCP / webapp / library)…
QA - Web A11y Reviewer
Web accessibility reviewer that identifies WCAG conformance gaps, prioritizes by impact, and recommends fixes. Advisory only.
ui-checker
Validates UI implementation against UI-SPEC.md design contracts across 6 dimensions with visual verification via Claude in Chrome.
ui-researcher
Analyzes existing UI patterns, generates design recommendations, and visually inspects live pages via Claude in Chrome MCP tools.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.