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-competitorgit 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-competitor)<a href="https://agentmods.dev/skills/oyusypenko/creo/creo-ux-competitor"><img src="https://agentmods.dev/badge/skills/oyusypenko/creo/creo-ux-competitor/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-competitor"><img src="https://agentmods.dev/badge/skills/oyusypenko/creo/creo-ux-competitor.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.00058 | $0.01127 |
| Opus 5 | $0.00029 | $0.00563 |
| Sonnet 5 | $0.00012 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
creo-ux-competitor 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor UX Analysis
Analyze external competitor websites to extract UX insights and learnings. Navigates competitor sites as a real user, documents their UX patterns, evaluates against professional standards, and identifies opportunities for differentiation.
Commands
| Command | Description |
|---|---|
/creo ux-competitor <url> |
Analyze a single competitor website |
/creo ux-competitor compare <url1> <url2> |
Compare two competitor websites |
Core Instructions
Configuration
- Check for project-specific config at
.claude/project-config.md - Read
competitors(pre-configured list by tier),reports_path - Load project extension if it exists at
.claude/skills/creo-ux-competitor/creo-ux-competitor-{project_id}.md. This file contains project-specific competitor list, positioning, differentiators, and analysis focus areas.{project_id}comes fromproject-config.md. Always load it before doing work. - If no config exists, ask user for competitor URL
Phase 1: Competitor Research
Before navigating, gather background info via web search:
- Company background and target audience
- Key features and value proposition
- User reviews (what people love and hate)
Identify key flows to analyze:
- Onboarding / Sign-up
- Core feature experience
- Pricing / Conversion
- Mobile experience
Phase 2: Live Analysis
Navigation strategy:
- Start at homepage
- Follow the primary user journey
- Screenshot every meaningful screen (use full page capture)
- Note micro-interactions and feedback
- Test on multiple viewports (375px mobile, 1440px desktop)
What to capture:
- First impressions (homepage)
- Sign-up / Onboarding flow
- Core feature experience
- Empty states and error handling
- Help / Support access
- Pricing presentation
Phase 3: Professional Evaluation
JTBD Analysis
When [situation], users want to [motivation], so they can [outcome].
Nielsen's Heuristics (Score 0-4)
| # | Heuristic | Questions |
|---|---|---|
| 1 | Visibility | Do users know what is happening? |
| 2 | Real world match | Is language familiar? |
| 3 | User control | Can users undo/cancel? |
| 4 | Consistency | Are patterns repeated? |
| 5 | Error prevention | Are mistakes prevented? |
| 6 | Recognition | Are options visible? |
| 7 | Flexibility | Are there shortcuts? |
| 8 | Minimalism | Is it clutter-free? |
| 9 | Error recovery | Are error messages helpful? |
| 10 | Help | Is guidance available? |
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 · 154 lines · 58 tokens per session scan A 31e2250405e1
creo-ux-competitor is a skill published in the GitHub repository oyusypenko/creo (4 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 1,127 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).
excalidraw
Generate Excalidraw diagrams from a compact DSL with brand-resolved colors. Use for boxes/arrows flow diagrams.