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 TimboGP/timbogp-marketplace --skill ux-foundationsgit 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/skills/timbogp/timbogp-marketplace/ux-foundations)<a href="https://agentmods.dev/skills/timbogp/timbogp-marketplace/ux-foundations"><img src="https://agentmods.dev/badge/skills/timbogp/timbogp-marketplace/ux-foundations/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/timbogp/timbogp-marketplace/ux-foundations"><img src="https://agentmods.dev/badge/skills/timbogp/timbogp-marketplace/ux-foundations.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.00119 | $0.00998 |
| Opus 5 | $0.00060 | $0.00499 |
| Sonnet 5 | $0.00024 | $0.00200 |
| Haiku 4.5 | $0.00012 | $0.00100 |
Grade A, and why
ux-foundations 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 12d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Foundations
Establish a coherent UX baseline in a project, adapted to whatever stack is present. This skill is the entry point for bootstrapping and the owner of the stack-detection convention every other implement skill reuses.
When to use
- Starting UX work in a new or existing repo with no established system.
- The user asks to "bootstrap", "set up", "establish", or "scaffold" UX/design foundations.
- Invoked by the
/ux-bootstrapcommand.
For narrower work, defer to the specialized skills: design-tokens, accessible-components, interaction-feedback, ux-copy. For evaluation rather than setup, use ux-audit, accessibility-audit, or ux-metrics.
Workflow
Always run these in order. Do not generate code before detection.
1. Detect the stack
Read references/stack-detection.md and follow it. Determine, in this order:
- Framework (React / Vue / Svelte / Angular / none)
- Styling approach (Tailwind / CSS Modules / styled-components or Emotion / vanilla CSS)
- Token output format that matches the above
- TypeScript yes/no
If nothing is detected (no package.json, no source), fall back to framework-agnostic HTML + CSS custom properties. Tell the user what you detected before writing anything.
2. Confirm scope
State a short plan and confirm the target. By default the baseline includes all five layers below; let the user opt out of any. Never overwrite existing files without showing a diff and confirming.
3. Lay the baseline (five layers)
- Design tokens — delegate to the
design-tokensskill. Produce a single source of truth (color with verified contrast, type scale, spacing scale, radius, shadow, motion durations/easings) in the format the stack expects. - Accessible base primitives — delegate to
accessible-components. Scaffold at minimum: an accessible Button, a labelled form Field, and a Dialog/Modal with focus management. Wire them to the tokens. - A11y linting — set up automated guardrails appropriate to the stack (e.g.
eslint-plugin-jsx-a11yfor React,eslint-plugin-vuejs-accessibilityfor Vue,svelte-check/a11y warnings for Svelte). Add the config and a script entry; do not silence existing warnings. - Lightweight metrics — delegate to
ux-metricsto add a minimal Core Web Vitals reporter (theweb-vitalssnippet) wired to the console or the project's analytics, so regressions are observable. - Interaction-feedback defaults — delegate to
interaction-feedbackto establish the empty/loading/error/success state pattern and an accessible toast/aria-liveregion the app can reuse.
What ships with it
2 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.
- 12d ago First seen · 65 lines · 119 tokens per session scan A 0fdf224950e5
ux-foundations is a skill published in the GitHub repository TimboGP/timbogp-marketplace (3 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 998 once invoked, about $0.0006 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
accessibility
Audits code for WCAG 2.2 AA compliance and provides design guidance for accessible components. Covers semantic HTML, ARIA, keyboard nav, contrast, focus management, and motion.
abd-design
ABD Design agent: produces architecture diagrams, component breakdowns, data flow, and design decisions from the current plan.
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
ux-review
Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
art-bible
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
unity-ui-patterns
Unity UI/UX pattern design-to-code translation. Screen flow architecture, View/ViewModel separation, HUD architecture, feedback & juice systems, dynamic list/grid views, transition & animation contracts. UI Toolkit only. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.