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 agentmods add skills/wojcikmm/spec-development-protocol/create-ui-componentnpx skills add WojcikMM/spec-development-protocol --skill create-ui-componentgit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWrote 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/wojcikmm/spec-development-protocol/create-ui-component)<a href="https://agentmods.dev/skills/wojcikmm/spec-development-protocol/create-ui-component"><img src="https://agentmods.dev/badge/skills/wojcikmm/spec-development-protocol/create-ui-component.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 | $0.00016 | $0.00304 |
| Opus 5 | $0.00008 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
create-ui-component 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 3d 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
Skill: Create UI Component
Purpose
Produce a reusable, accessible, and testable UI component that aligns with the project's design system and conventions.
Prerequisites
- Component purpose, props, and states are defined in the design spec.
- UI framework and design system are defined in
TECH.md.
Checklist
- Component Design: Follow single responsibility. Define the props/interface first. Provide default props.
- Implementation: Keep the component pure. Extract complex logic to a custom hook. Use design system tokens, not inline styles. Handle all visual states (loading, empty, error).
- Accessibility (a11y): Use semantic HTML. Ensure keyboard navigation. Add ARIA attributes only when necessary. Don't rely on color alone to convey state.
- State Management: Use local state first. Lift state only when needed. Use global state for app-wide concerns.
- Testing: Test rendered output and user interactions, not implementation details. Cover all visual states. Use accessible queries. Mock external dependencies.
- Documentation: Add JSDoc for complex props. Export from the barrel file.
Quality Bar
- Renders correctly in all visual states.
- Keyboard-operable and accessible.
- Tested for each state and user interaction.
- No hardcoded styles outside the design system.
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.
- 3d ago First seen · 32 lines · 16 tokens per session scan A ac96b678a569
create-ui-component is a skill published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 22d ago), licensed MIT. It adds 16 tokens to every session and 304 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…