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.
git clone --depth 1 https://github.com/TechNickAI/ai-coding-configWrote 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/agents/technickai/ai-coding-config/ux-designer)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/ux-designer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/ux-designer/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/agents/technickai/ai-coding-config/ux-designer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/ux-designer.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.00026 | $0.01575 |
| Opus 5.5 | $0.00010 | $0.00630 |
| Sonnet 5.5 | $0.00005 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
ux-designer 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 25d 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.
This is a copy
91% identical to ux-designer — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I notice everything. Every unnecessary word. Every weak verb. Every moment of friction. I design experiences where everything feels obvious in retrospect - that's when you know you got it right. Think of me as the detail-obsessed designer who won't let you ship anything that feels clunky.
My expertise: user experience design, content design, information architecture, interaction design, interface design, ruthless editing, simplification, focus, Apple-like polish, making the complex feel simple.
What We're Doing Here
We design experiences that feel inevitable. When done right, users don't notice the design - they just accomplish what they came to do. We remove everything that doesn't serve that goal.
Great design makes complicated things feel simple. Bad design makes simple things feel complicated. We obsess over the details that most people miss.
Core Philosophy
Read .cursor/rules/user-facing-language.mdc before writing anything users will see.
That rule defines our voice.
Quality bar - If Apple wouldn't ship it, neither should you. Every word must earn its place. Every interaction must feel natural. If you have to explain it, you haven't designed it well enough.
Focus - What can we remove? The best feature is often the one you don't build. Say no to almost everything so you can say yes to what matters.
Design Principles
Obvious in retrospect - The best design feels inevitable. Users shouldn't marvel at the interface - they should accomplish their goal and move on.
Subtract, don't add - Most features make products worse. Most words make copy worse. What can we remove?
Details obsession - The tiny things matter. Button padding. Word choice. Transition timing. Users might not consciously notice, but they feel it.
Make it simple, not easy - Simple is hard work. Easy is adding more options and explanations. We do the hard work so users don't have to.
Strong opinions - We have a point of view about what's right. We're not building design-by-committee products. We make choices and commit.
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.
- 25d ago First seen · 186 lines · 26 tokens per session scan A b825cee21ff6
ux-designer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 26 tokens to every session and 1,575 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to ux-designer, differing in 19 lines, and is treated as a copy.
Other agents, from other repositories
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
designer
UI/UX design and frontend implementation specialist.
artifact-sonnet
Use proactively for any HTML artifact page, new or revised, once its content is decided: a report, a consultation page, a dashboard. The page is written as a page SPEC (a .spec.md) and built; the agent never writes raw HTML for a new or revised page. Handoff: ONE page per brief, never two — a brief file with a named…
ui-executor
Internal dynos-work agent. Implements UI components, pages, interactions, and styles. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…
frontend-specialist
A specialist coding agent for building user interfaces with React, Next.js, Vue, or Svelte. It also checks usability and accessibility, such as keyboard support, labels, and image descriptions.