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.
git 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/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing)<a href="https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.03465 |
| Opus 5.5 | $0.00000 | $0.01386 |
| Sonnet 5.5 | $0.00000 | $0.00693 |
| Haiku 4.5 | $0.00000 | $0.00347 |
Grade A, and why
frontend-testing 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 1mo 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 — 222 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-testing.md.
Referenced context:
../../ai/rules/frontend-rules.md../../ai/rules/testing-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-testing
Canonical Skill: ai/skills/frontend-testing.md
Frontend Testing
Use for Vitest, Testing Library, API-domain tests, coverage, Storybook, and Playwright E2E.
Read First
ai/rules/frontend-rules.mdai/rules/testing-rules.mdai/rules/frontend-quality-rules.mdai/architecture/web-architecture.md
Workflow
- Test observable behavior at the narrowest public boundary and place it in the nearest established
__tests__folder. - Use accessible queries and shared API/E2E helpers; cover cancellation and recoverable failures where relevant.
- Keep global statements, branches, functions, and lines thresholds at 90%.
- Run the targeted test first, then coverage, Storybook, or the relevant E2E split for the changed surface.
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.
- 1mo ago First seen · 222 lines · 0 tokens per session scan A 73119bc3038e
frontend-testing is a cursor rule published in the GitHub repository williamisnotdefined/rubiks-cube-solver (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,465 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
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
30-testing
Convenciones de testing, cobertura mínima, tipos de tests, mocks.
tester
Tester role - Unit, E2E, and visual regression testing.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.