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-visualizationgit 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.02838 |
| Opus 5 | $0.00000 | $0.01419 |
| Sonnet 5 | $0.00000 | $0.00568 |
| Haiku 4.5 | $0.00000 | $0.00284 |
Grade A, and why
frontend-visualization 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.
This is a copy
86% identical to frontend-state-management — 106 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 199 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-visualization.md.
Referenced context:
../../ai/rules/frontend-rules.md../../ai/rules/frontend-quality-rules.md../../ai/architecture/frontend-visualization.md../../ai/architecture/rubiks-cube-visualization-package.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-visualization
Canonical Skill: ai/skills/frontend-visualization.md
Frontend Visualization
Use for cube rendering, playback, visualization adapters, or scan visualization.
Read First
ai/rules/frontend-rules.mdai/rules/frontend-quality-rules.mdai/architecture/frontend-visualization.mdai/architecture/rubiks-cube-visualization-package.md
Workflow
- Identify the owning puzzle/page context and preserve the Rust solver boundary.
- Use the active package's narrow puzzle subpath; keep imperative rendering sync in focused hooks/refs.
- Keep scanner evidence and reviewed stickers in typed scan contracts, with disclosure before camera permission and automatic analysis after permission.
- Verify rendering, cancellation, accessibility, reduced motion, mobile sizing, and the relevant solve/scan E2E flow.
Referenced Context
Reference: ai/rules/frontend-rules.md
Frontend Rules
Boundaries
- Keep solving, notation semantics, puzzle validity, and replay verification in Rust. React renders and coordinates typed product workflows.
- Keep HTTP mechanics and normalization in
apps/web/src/api; UI consumes domain hooks/adapters. - Typed scan-session contracts MAY contain reviewed stickers, confidence, and manual overrides. Notation solve UI MUST NOT expose facelet, Kociemba, or raw cube-state inputs.
- Keep API load, form, page workflow, solve result, scanner review, and visualization playback state separately owned unless a focused page owner coordinates them.
- Use the active
@rubiks-cube-solver/rubiks-cubepackage as a visualization adapter, never as canonical solver state.
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 · 199 lines · 0 tokens per session scan A 2d13eb7a0a8f
frontend-visualization is a cursor rule published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,838 tokens. A static security scan graded it A with 0 findings. It is 86% identical to frontend-state-management, differing in 106 lines, and is treated as a copy.
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.