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/TimboGP/timbogp-marketplaceWrote 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/plugins/timbogp/timbogp-marketplace/ux-design)<a href="https://agentmods.dev/plugins/timbogp/timbogp-marketplace/ux-design"><img src="https://agentmods.dev/badge/plugins/timbogp/timbogp-marketplace/ux-design/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/plugins/timbogp/timbogp-marketplace/ux-design"><img src="https://agentmods.dev/badge/plugins/timbogp/timbogp-marketplace/ux-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ux-design 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 10d 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
{
"name": "ux-design",
"version": "0.4.0",
"description": "Guide, measure, and implement UX best practices in Claude Code. Scored usability + accessibility audits, quantitative UX metrics, and stack-adaptive scaffolding for design tokens, accessible components, interaction feedback, and UX copy.",
"author": {
"name": "TimboGP"
},
"homepage": "https://github.com/TimboGP/timbogp-marketplace",
"repository": "https://github.com/TimboGP/timbogp-marketplace",
"license": "MIT",
"keywords": [
"ux",
"ui",
"accessibility",
"wcag",
"design-system",
"design-tokens",
"usability",
"ux-writing",
"core-web-vitals"
]
}
What it installs
The manifest is a name and a version. 9 skills, 5 commands, 1 agent travel with it, and installing the plugin installs all of them — 1,406 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill accessibility-audit A 107 tokens
- Skill design-tokens A 98 tokens
- Skill accessible-components A 98 tokens
- Skill interaction-feedback A 103 tokens
- Skill ux-audit A 84 tokens
- Skill ux-metrics A 101 tokens
- Skill ux-copy A 85 tokens
- Skill ux-foundations A 119 tokens
- Skill ux-onboarding A 145 tokens
- Command ux-audit A 22 tokens
- Command ux-bootstrap A 35 tokens
- Command ux-onboarding A 43 tokens
- Command ux-help A 26 tokens
- Command ux-review A 30 tokens
- Agent ux-reviewer A 310 tokens
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.
- 10d ago First seen · 23 lines scan A f73ead84335f
ux-design is a plugin published in the GitHub repository TimboGP/timbogp-marketplace (3 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
accessibility
WCAG 2.2 AA accessibility auditing and design guidance. Review mode audits existing code; design mode guides building accessible components.
base-ui-react
MUI Base UI unstyled React components with Floating UI. Use for accessible components, Radix UI migration, render props API, or encountering positioning, popup, v1.0 beta issues.
frontend-design
Production-grade frontend design skill that avoids AI slop — specific rules for typography, color (OKLCH), layout, motion, interaction, and UX writing.
gan-zhong-xue
A learning add-on that turns AI-made code changes into guided, explainable understanding. It uses a question-and-answer process so developers can restate the reasoning and apply it elsewhere.
requirements-generator
Generates structured requirements documents from a project idea or feature description, including functional requirements, non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items.
agent-based-development
Full async multi-agent development workflow: Planning → Design → Dev → Security/Tech Review loop with file-based handoffs and release-branch Git model.