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.
npx skills add oyusypenko/creo --skill creo-ux-internalgit 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/skills/oyusypenko/creo/creo-ux-internal)<a href="https://agentmods.dev/skills/oyusypenko/creo/creo-ux-internal"><img src="https://agentmods.dev/badge/skills/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/skills/oyusypenko/creo/creo-ux-internal"><img src="https://agentmods.dev/badge/skills/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.00069 | $0.01205 |
| Opus 5 | $0.00034 | $0.00602 |
| Sonnet 5 | $0.00014 | $0.00241 |
| Haiku 4.5 | $0.00007 | $0.00120 |
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 11d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal UX Analysis
Analyze your own application by combining existing screenshots, code reading, and live UI testing. Documents findings using JTBD framework, Nielsen's heuristics, and journey maps, then proposes concrete simplifications.
Commands
| Command | Description |
|---|---|
/creo ux-internal <flow> |
Analyze a specific feature or flow |
/creo ux-internal full |
Full application UX analysis |
Core Instructions
Configuration
- Check for project-specific config at
.claude/project-config.md - Read
dev_server_url(default:http://localhost:3000),screenshots_path,reports_pathc3. Load project extension if it exists at.claude/skills/creo-ux-internal/creo-ux-internal-{project_id}.md. This file contains project-specific user flows, JTBD, domain terminology, and feature mapping.{project_id}comes fromproject-config.md. Always load it before doing work. - If no config exists, use defaults or ask user
Phase 0: Screenshot Analysis (Do First)
Check for existing screenshots in screenshots/ or .claude/screenshots/.
- Read all screenshots using the Read tool (multimodal)
- Create initial observations table: Screenshot, First Impression, Obvious Issues, Questions
- Identify patterns across screens (consistency issues, repeated problems)
- Note specific elements that need live testing verification
- Document hypotheses to verify in Phase 2
What to look for in screenshots:
- Visual hierarchy: Is the most important info prominent?
- Information density: Too much or too little on screen?
- Button placement: Are CTAs obvious and accessible?
- Form design: Are fields grouped logically?
- Navigation clarity: Can user understand where they are?
- Error states, empty states, loading states
- Mobile readiness
Phase 1: Code Analysis
Read project overview and architecture rules first. Then analyze:
- Data models and relationships
- State management patterns
- API endpoints and data flow
- Decision points and branches
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.
- 11d ago First seen · 152 lines · 69 tokens per session scan A 6d99a43cdfeb
creo-ux-internal is a skill published in the GitHub repository oyusypenko/creo (4 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 1,205 once invoked, about $0.0003 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 skills, from other repositories
agent-loop-ext
Crash-resilient external agent loop with state persistence and CI/CD integration.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
ci-status
Show current pipeline status for the active branch (GitLab CI or GitHub Actions).
devops
DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.