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 PracticalSwan/agent-skills --skill stitch-react-componentsgit clone --depth 1 https://github.com/PracticalSwan/agent-skillsWrote 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/practicalswan/agent-skills/stitch-react-components)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/stitch-react-components"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/stitch-react-components.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.1 | $0.00037 | $0.01319 |
| Opus 5 | $0.00018 | $0.00660 |
| Sonnet 5 | $0.00007 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
stitch-react-components 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 today.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stitch React Components
This skill is a catalog-normalized import from https://github.com/google-labs-code/stitch-skills at commit 7b53207b94e62911777d53d4238b5f8c88c2b519, source path plugins/stitch-build/skills/react-components. The upstream control file was corrected for this workspace: the verified Stitch MCP surface here is design-system oriented, so screen lookup, screen generation, and screen editing tools must be used only when the current host explicitly exposes them.
When to Use This Skill
- Use when a Stitch screen or export should become modular React components or an existing React surface must be synchronized with newer Stitch evidence.
- The task involves Google Stitch project IDs,
.stitch/artifacts, DESIGN.md files, Stitch exports, or Stitch-specific validation. - The broader
stitch-designrouter points here as the narrowest workflow.
Workflow
- Acquire source HTML and screenshots from
.stitch/designs/, Stitch web exports, or current host-listed screen tools. - Do not assume
get_screenorlist_screensexists in this workspace. - Record available project and screen identifiers plus the sync timestamp in
.stitch/metadata.jsonwhen that evidence exists. - Extract current color, typography, spacing, and radius tokens from the exported HTML before editing components.
- Move static copy, image URLs, and lists into
src/data/mockData.ts. - Create small components with
Readonlyprop interfaces and isolate interactions in hooks. - Map Stitch theme values into Tailwind/theme tokens, replace placeholder links with real application routes, and cover dark-mode states instead of scattering raw hex values.
- Run the bundled validator where dependencies are available, then run the app build or dev check.
Local Assets
examples/,resources/,references/, orreference/are upstream support material when present. TreatSKILL.mdas the source of truth if a support file mentions an unavailable MCP tool.scripts/are optional helpers. On Windows, prefer PowerShell or Node equivalents unless Git Bash or WSL is actually available.- Keep generated
.stitch/files out of commits unless the user explicitly wants them as durable examples.
What ships with it
11 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.
- CHANGELOG.md 6.1 KB
- examples/gold-standard-card.tsx 1.9 KB
- LICENSE.txt 11 KB
- package-lock.json 7.0 KB
- package.json 355 B
- resources/architecture-checklist.md 613 B
- resources/component-template.tsx 1.0 KB
- resources/stitch-api-reference.md 1.2 KB
- resources/style-guide.json 496 B
- scripts/fetch-stitch.sh 1009 B runs code
- scripts/validate.js 2.7 KB runs code
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.
- today Changed e78b0aa5c96a
- 2d ago Changed 1342c314d371
- 4d ago First seen · 91 lines · 37 tokens per session scan A 5dabef87a2fc
stitch-react-components is a skill published in the GitHub repository PracticalSwan/agent-skills (13 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,319 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
ranui
Use when building UI with the ranui web-component library (elements like , , , , ) or its fluent DOM builder (ranui/builder — Div/View/Span/signal/createEffect/EventManager). Covers the import map, the full element inventory, conventions, accessibility, and where the authoritative API reference lives.
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
ai-ui-generation
AI-assisted UI generation patterns for json-render, v0.app, Google Stitch, Bolt Cloud, and Cursor workflows. Covers prompt engineering for component and full-stack app generation, review checklists for AI-generated code, design token injection, refactoring for design system conformance, and CI gates for quality…
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…