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 commands/halflength-ampleness75/claude-code-recipes/component-gengit clone --depth 1 https://github.com/halflength-ampleness75/claude-code-recipesWrote 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/commands/halflength-ampleness75/claude-code-recipes/component-gen)<a href="https://agentmods.dev/commands/halflength-ampleness75/claude-code-recipes/component-gen"><img src="https://agentmods.dev/badge/commands/halflength-ampleness75/claude-code-recipes/component-gen.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.00015 | $0.01318 |
| Opus 5 | $0.00008 | $0.00659 |
| Sonnet 5 | $0.00003 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
component-gen 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 5d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a production-quality UI component from the description provided in $ARGUMENTS.
Step 1 — Parse the Request
Extract from $ARGUMENTS:
- Component name (e.g., "DataTable", "Modal", "SearchBar")
- Feature requirements (what the component should do)
- Framework preference (React or Vue — detect from project if not stated)
- Variants or states (e.g., "loading, error, empty states")
If the description is minimal (e.g., just "Modal"), generate a fully-featured, accessible version with sensible defaults.
Step 2 — Detect Project Conventions
Search the project to determine:
- Framework: React (JSX/TSX) or Vue (SFC
.vuefiles). Checkpackage.jsonforreact,vue,next,nuxt, etc. - Language: TypeScript or JavaScript. Check for
tsconfig.json, existing file extensions. - Styling approach: CSS Modules, Tailwind CSS, styled-components, Emotion, SCSS, plain CSS, or a UI library (shadcn/ui, MUI, Chakra, Vuetify, etc.). Check existing components.
- State management: React hooks, Zustand, Redux, Pinia, Vuex.
- Component patterns: Read 1-2 existing components to match:
- File naming convention (
PascalCase.tsx,kebab-case.vue) - Directory structure (flat, feature-based, atomic design)
- Export patterns (default export vs named export)
- Props definition pattern (interface, type, defineProps)
- File naming convention (
Step 3 — Design the Component API
Before writing code, define the component's public interface:
## Component Design: [Name]
### Props
| Prop | Type | Default | Required | Description |
|------|------|---------|----------|-------------|
| ... | ... | ... | ... | ... |
### Events / Callbacks
| Event | Payload | Description |
|-------|---------|-------------|
| ... | ... | ... |
### Slots / Children (if applicable)
| Slot | Description |
|------|-------------|
| ... | ... |
### States
- Default, Loading, Error, Empty, Disabled (as applicable)
Step 4 — Generate the Component
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.
- 5d ago First seen · 164 lines · 15 tokens per session scan A b7171a17889d
component-gen is a command published in the GitHub repository halflength-ampleness75/claude-code-recipes (2 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,318 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 commands, from other repositories
dare-frontend-design
Arquitetura frontend DARE para projetos React e Vue. Detecta god components, fetch inline em JSX/template, e gera scaffold DARE-compliant.
bundle-analyze
Tu es un expert performance React. Tu dois analyser la taille du bundle, identifier les dépendances volumineuses et proposer des optimisations.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
generate-hook
Génération Custom Hook React.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.