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 Eliyce/paqad-ai --skill ux-design-researchgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/ux-design-research)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/ux-design-research"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/ux-design-research/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/eliyce/paqad-ai/ux-design-research"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/ux-design-research.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.00016 | $0.00544 |
| Opus 5 | $0.00008 | $0.00272 |
| Sonnet 5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
ux-design-research 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Collects external and internal UI references for high-scope interface work, translating them into concrete guidance on flows, states, and interaction patterns rather than mood-board commentary.
Use This When
Use this only for full-lane work that also changes screens, components, or major redesigns. It should not activate for non-UI work or small graduated-lane interface adjustments.
Inputs
- Read the request, current UI docs, and affected flow or screen inventory first.
- Read
references/research-capture-format.mdbefore gathering examples so findings stay structured. - Read the stack-specific browser validation guide that matches the project surface.
Procedure
- Define the target interaction, user goal, and constraints before collecting references.
- Gather only sources that inform navigation, state handling, feedback, or visual hierarchy for the changed flow.
- Summarize each useful reference in terms of the concrete behavior it suggests, not just aesthetics.
- Translate findings into project-specific recommendations tied to states, flows, and validation needs.
- Call out any internal pattern conflict or accessibility concern revealed by the research.
Output Contract
- Match
assets/output.template.md:## Research Targets,## Reference Findings,## Recommended Directions. - Every Reference Finding states Pattern and Why it matters here; never aesthetics-only.
- Sources must be dated and quoted minimally — no long quotations.
- Output must pass
scripts/lint-output.sh(exit 0).
Escalate / Stop Conditions
- Ask when the design goal or target user is too vague to choose meaningful references.
- Warn when research points toward a pattern that conflicts with established product constraints or accessibility needs.
- Do not present external inspiration as a mandate without mapping it to the project context.
Resources
references/research-capture-format.mdscripts/lint-output.shassets/output.template.mdruntime/capabilities/coding/stacks/laravel/references/tools/playwright.mdagents/openai.yaml
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 68 lines · 16 tokens per session scan A fa5f4a5925f7
ux-design-research is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 544 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-09-03.
Other skills, from other repositories
double-diamond
A four-stage design method for understanding a problem, defining it clearly, exploring possible solutions, and choosing one to deliver.
make-interfaces-feel-better
Use when building or reviewing UI polish: typography, hit areas, nested radius, optical alignment, shadows, media outlines, micro-interactions, and animation performance.
frontend-skill
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
frontend-skill
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
infographics
Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.