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 fall-out-bug/sdp --skill uxgit clone --depth 1 https://github.com/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/ux)<a href="https://agentmods.dev/skills/fall-out-bug/sdp/ux"><img src="https://agentmods.dev/badge/skills/fall-out-bug/sdp/ux/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/fall-out-bug/sdp/ux"><img src="https://agentmods.dev/badge/skills/fall-out-bug/sdp/ux.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.00014 | $0.00921 |
| Opus 5.5 | $0.00006 | $0.00368 |
| Sonnet 5.5 | $0.00003 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
ux 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@ux - UX Research
Structured UX findings that @design consumes as acceptance criteria. Not "what UI do you want?" — mental model elicitation.
EXECUTE THIS NOW
When user invokes @ux {feature-id} or when @feature auto-triggers it (user-facing features only):
Phase 1: Listening Session (6 Questions)
These are mental model elicitation questions, not UI specification:
-
Context of reach: "What is the user doing in the 10 minutes before they encounter this feature? What problem are they mid-solving?"
-
Mental model gap (Don Norman: Gulf of Execution): "What will the user think happens when they perform the primary action? Where does that model likely diverge from what the system actually does?"
-
Workaround reality: "What do users do today without this feature? The workaround reveals the existing mental model."
-
Friction prediction: "At which step will most users pause, hesitate, or abandon? What makes that moment hard?"
-
Thinking style spectrum (Indi Young): "Who is the cautious user who double-checks everything vs. the fast mover who skips instructions? Does the design need to serve both?"
-
Accessibility context: "Who might be excluded by the obvious implementation? (screen reader, keyboard-only, low bandwidth, cognitive load under stress)"
Phase 2: Autonomous Codebase Research
Use codebase access (no human UX researcher has this):
- Scan for existing features with similar user-visible surfaces → find established patterns to follow
- Check for existing accessibility patterns in the codebase
- Cross-reference stated pain points against current error handling → flag "user sees generic error when X happens"
- Flag technical decisions in @idea's output that will create Gulf of Execution/Evaluation problems
- Generate UX Risk Register: a ranked list of user-visible failure modes
Output: docs/ux/{feature}.md
Create file with YAML frontmatter and prose sections. @design reads this when present and converts friction_points and ux_risks into acceptance criteria.
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 · 111 lines · 14 tokens per session scan A 8db7e87d36bf
ux is a skill published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 921 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component Prismer HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
baoyu-design
Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks (a.k.a. PPT / PowerPoint presentations), documents and résumés, animations, 3D objects, research reports, HTML email, diagrams, fliers, and visual…
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
logo-generator
Deprecated compatibility entry for Logo construction. This component is now maintained in Bricks; install and use component-builder to build a new Logo.