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/williamisnotdefined/rubiks-cube-solver/frontend-componentizationnpx skills add williamisnotdefined/rubiks-cube-solver --skill frontend-componentizationgit clone --depth 1 https://github.com/williamisnotdefined/rubiks-cube-solverWrote 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/williamisnotdefined/rubiks-cube-solver/frontend-componentization)<a href="https://agentmods.dev/skills/williamisnotdefined/rubiks-cube-solver/frontend-componentization"><img src="https://agentmods.dev/badge/skills/williamisnotdefined/rubiks-cube-solver/frontend-componentization.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.00023 | $0.03061 |
| Opus 5 | $0.00012 | $0.01530 |
| Sonnet 5 | $0.00005 | $0.00612 |
| Haiku 4.5 | $0.00002 | $0.00306 |
Grade A, and why
frontend-componentization 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 4d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated from ai/registry.json. Do not edit manually.
Canonical skill: ../../../ai/skills/frontend-componentization.md.
Referenced context:
../../../ai/rules/frontend-component-rules.md../../../ai/rules/frontend-rules.md../../../ai/rules/frontend-styling-rules.md../../../ai/rules/frontend-quality-rules.md../../../ai/architecture/web-architecture.md
This file is compiled from canonical AI knowledge files. Edit canonical files under ai, then run npm run ai:sync.
Compiled AI Skill: frontend-componentization
Canonical Skill: ai/skills/frontend-componentization.md
Frontend Componentization
Use for React component extraction, shared primitives, page composition, and Storybook surfaces.
Read First
ai/rules/frontend-component-rules.mdai/rules/frontend-rules.mdai/rules/frontend-styling-rules.mdai/rules/frontend-quality-rules.mdai/architecture/web-architecture.md
Workflow
- Locate the bounded context and identify the concrete ownership or reuse benefit.
- Keep page-specific code local; promote only demonstrated cross-context UI.
- Preserve semantics, focus/keyboard behavior, state ownership, and the established shadcn-compatible visual language.
- Run targeted tests, Storybook build when stories change, then web build and lint.
Referenced Context
Reference: ai/rules/frontend-component-rules.md
Frontend Component Rules
- Keep route files readable as composition and keep context-specific components/hooks under their owning
src/pages/<Context>tree. - Move code to
src/componentsonly after a real cross-context consumer exists. Keep context-independent helpers focused and directly imported. - Extract when repetition, a named responsibility, or a state boundary justifies it; do not replace a god component with a god hook/provider.
- Use native semantics first and existing shared primitives for dialogs, sheets, selects, switches, checkboxes, menus, toasts, popovers, tabs, and tooltips.
- Preserve explicit small props,
childrenfor layout composition, keyboard/focus behavior, and accessible names. - Use
lucide-reactfor UI icons rather than local SVG component/path markup. - Keep stories in nearby
stories/folders and tests in nearby__tests__/folders. Use controls instead of one story per prop. - Do not couple component organization to locale-specific route variants; established slugs remain stable across locales.
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.
- 4d ago First seen · 196 lines · 23 tokens per session scan A 542df617cc54
frontend-componentization is a skill published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 10d ago), licensed MIT. It adds 23 tokens to every session and 3,061 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
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
flags
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.