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 agentmods add skills/leifericf/agentic-sdk/design-uxnpx skills add leifericf/agentic-sdk --skill design-uxgit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/design-ux)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/design-ux"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/design-ux.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.00489 |
| Opus 5 | $0.00006 | $0.00244 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
design-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 5d 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.
What it actually says
design-ux
Establish UX guardrails, visual direction, and interaction patterns across web, mobile, desktop, TUI, and CLI surfaces. Reduce interface entropy with reusable rules. UI only.
Procedure
- Read
project-meta.md,problem-description.md,product-requirements.md,risk-assumption-review.md,decision-log.md, andopen-questions.md. If a prerequisite is missing, returnblocked: <which artifact>. - Run the applicability gate. If the project has no user-facing surface (pure
library, backend-only service, batch job, data pipeline), do not produce the
artifact. Append a
decision-log.mdrow: decision "Skip UX design guide", why "no user-facing surfaces in scope", tradeoff "revisit if a UI is added". Returnskipped: no user-facing surface. - Surface and resolve
[Blocking]items affectingux-design-guide.md. - Collect three to five visual references (URLs, screenshots, CLI or TUI tools, or a textual direction). If none, pick a direction: Minimal, Editorial, Playful, Enterprise, Retro, or Luxury.
- Clarify, at most three per turn: primary interface surfaces, brand tone, density, target users and context, accessibility expectations, input modalities, offline and latency constraints. Do not assume UI toolkits unless already decided.
- Record new decisions in
decision-log.md. - Write
~/.agentic-sdk/<project>/artifacts/planning/ux-design-guide.mdwith: Metadata, Visual References, Design Principles, Interface Surfaces, Accessibility, Typography, Color System, Layout Rules, Components, CLI/TUI Conventions (if applicable), Interaction Patterns, Content Style, UI Definition of Done.
Boundaries
Owns interaction and visual guardrails. design-technical owns system architecture and the stack. Runs only when a user-facing surface exists. Reached by plan-system.
Return
One line: the artifact written (or skipped: no user-facing surface) and a
terse status, or blocked: <reason>.
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.
- 5d ago First seen · 47 lines · 12 tokens per session scan A 50e34f39fa64
design-ux is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 489 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…