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 HappyDoggyAI/superui --skill superui-tddgit clone --depth 1 https://github.com/HappyDoggyAI/superuiWrote 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/happydoggyai/superui/superui-tdd)<a href="https://agentmods.dev/skills/happydoggyai/superui/superui-tdd"><img src="https://agentmods.dev/badge/skills/happydoggyai/superui/superui-tdd/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/happydoggyai/superui/superui-tdd"><img src="https://agentmods.dev/badge/skills/happydoggyai/superui/superui-tdd.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.00067 | $0.00941 |
| Opus 5 | $0.00034 | $0.00470 |
| Sonnet 5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
superui-tdd 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Frontend Implementation
Implement frontend UI through strict test-driven development. Do not skip RED, and do not silently drift from DESIGN.md.
Core Rules
- RED cannot be skipped: write a failing test, see it fail, then implement.
DESIGN.mdis the only design truth source. Colors, type, spacing, radius, and shadows must use its tokens.RESPONSIVE_RULES.mdis a hard constraint. Code violating a MUST NOT rule must be rewritten.- Any deviation from DESIGN.md must be recorded in
design-adjustments.mdwith reason and fallback. - Tests and tracking artifacts use
<ARTIFACT_ROOT>; implementation code goes in the target project. - Read
skills/superui-shared/TASK_MANAGEMENT.md; updatetodo.md, append RED/GREEN/REFACTOR evidence toprogress.md, and updatepipeline-status.md.
Required Inputs
| File | Source | Purpose |
|---|---|---|
DESIGN.md |
superui-design-md | tokens and design rules |
specs/*.md |
superui-planner | GIVEN/WHEN/THEN behavior |
test-plan.md |
superui-planner | test scope and standards |
proposal.md or design-proposal.md |
superui-planner | implementation order and component tree |
Read skills/superui-shared/RESPONSIVE_RULES.md before coding.
Workflow
- Preflight: load required inputs and responsive rules.
- RED: write one failing test suite for one component or behavior.
- GREEN: write the smallest implementation that passes the failing test.
- REFACTOR: improve code while keeping all tests green.
- Repeat for the next component or behavior.
- Validate visual, interaction, accessibility, and responsive requirements.
- Record deviations in
design-adjustments.md.
Test Layers
| Layer | Preferred tools | Fallback |
|---|---|---|
| Visual contract | Playwright + pixelmatch or screenshot comparison | Manual comparison against DESIGN.md previews |
| Interaction behavior | Playwright + Testing Library | Cypress |
| Accessibility | axe-core + Playwright | pa11y or manual WCAG checklist |
What ships with it
1 file 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.
- 10d ago First seen · 98 lines · 67 tokens per session scan A a3252d207bb8
superui-tdd is a skill published in the GitHub repository HappyDoggyAI/superui (2 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 941 once invoked, about $0.0003 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
react-web
React web development with hooks, React Query, Zustand.
review-screenshot
A standard workflow for taking screenshots to check a user interface, using a dedicated review process for different verification modes.
figma-to-react-workflow
Orchestrates end-to-end Figma-to-React conversion pipeline with enforced TDD, automated pixel-diff visual QA, E2E testing, and app-type awareness (web apps, Chrome extensions, PWAs). Keywords: Figma to React, design tokens, autonomous component generation, Figma conversion, Tailwind config, component library, TDD…
tdd-from-figma
Writes failing tests FIRST from Figma structure and the design token lockfile, then implementation makes them pass. Per-component TDD cycle using exact values from design-tokens.lock.json. App-type-aware: generates Chrome extension, PWA, and web app test templates. Keywords: TDD, test-driven development, Figma tests…
web-dev-standards
Use when designing software architectures ('codebase-design' Deep Modules/Design-It-Twice), writing tests ('test-driven-development' mock boundaries), creating setup scripts ('interactive-wizard'), TypeScript standards, Next.js, Expo, or Monorepos.
fec-tdd-workflow
A frontend test-driven development workflow, or TDD, describes the expected behavior with a failing test, implements the smallest change to pass it, and then refactors. It covers UI components, hooks, API clients, route guards, and user workflows.