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-form-validationnpx skills add williamisnotdefined/rubiks-cube-solver --skill frontend-form-validationgit 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-form-validation)<a href="https://agentmods.dev/skills/williamisnotdefined/rubiks-cube-solver/frontend-form-validation"><img src="https://agentmods.dev/badge/skills/williamisnotdefined/rubiks-cube-solver/frontend-form-validation.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.1 | $0.00023 | $0.02420 |
| Opus 5 | $0.00012 | $0.01210 |
| Sonnet 5 | $0.00005 | $0.00484 |
| Haiku 4.5 | $0.00002 | $0.00242 |
Grade A, and why
frontend-form-validation 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 6d 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.
Generated from ai/registry.json. Do not edit manually.
Canonical skill: ../../../ai/skills/frontend-form-validation.md.
Referenced context:
../../../ai/rules/frontend-rules.md../../../ai/rules/frontend-form-rules.md../../../ai/rules/frontend-quality-rules.md../../../ai/architecture/api-boundary.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-form-validation
Canonical Skill: ai/skills/frontend-form-validation.md
Frontend Form Validation
Use for solve controls, inputs, local limits, scanner review controls, and form submission behavior.
Read First
ai/rules/frontend-rules.mdai/rules/frontend-form-rules.mdai/rules/frontend-quality-rules.mdai/architecture/api-boundary.md
Workflow
- Separate lightweight UX validation from API/engine semantics.
- Choose local state or existing RHF/Zod usage based on the actual form, not a mandatory setup.
- Keep notation forms raw-state-free and scan corrections inside typed scan sessions.
- Verify accessible errors, blocked invalid requests, API outcomes, and relevant E2E behavior.
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.
Web Runtime And 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.
- 6d ago First seen · 164 lines · 23 tokens per session scan A 7c2f60d61b75
frontend-form-validation is a skill published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 2,420 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…