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 rules/williamisnotdefined/rubiks-cube-solver/frontend-componentizationgit clone --depth 1 https://github.com/williamisnotdefined/rubiks-cube-solverWhat 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.00000 | $0.03084 |
| Opus 5 | $0.00000 | $0.01542 |
| Sonnet 5 | $0.00000 | $0.00617 |
| Haiku 4.5 | $0.00000 | $0.00308 |
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 2d 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 — 197 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.
- 2d ago First seen · 197 lines · 0 tokens per session scan A 27630a9f37cd
frontend-componentization is a cursor rule published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,084 tokens. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.