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/react-query-request-hooks)<a href="https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/react-query-request-hooks"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/react-query-request-hooks/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/react-query-request-hooks"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/react-query-request-hooks.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.02366 |
| Opus 5.5 | $0.00000 | $0.00946 |
| Sonnet 5.5 | $0.00000 | $0.00473 |
| Haiku 4.5 | $0.00000 | $0.00237 |
Grade A, and why
react-query-request-hooks 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 — 166 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/react-query-request-hooks.md.
Referenced context:
../../ai/rules/frontend-rules.md../../ai/rules/frontend-api-hook-rules.md../../ai/rules/api-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: react-query-request-hooks
Canonical Skill: ai/skills/react-query-request-hooks.md
React Query Request Hooks
Use for web request functions, runtime response validation, query/mutation hooks, and query keys.
Read First
ai/rules/frontend-rules.mdai/rules/frontend-api-hook-rules.mdai/rules/api-rules.mdai/architecture/api-boundary.md
Workflow
- Follow the owning API domain's current layout and keep transport code under
src/api/client. - Preserve typed API failures, transport errors, cancellation, and cache ownership.
- Expose hooks/adapters to UI, not raw requests or query keys.
- Add tests in the nearest API-domain
__tests__, then run targeted tests and web build.
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
- Preserve static rendering for indexable routes,
hydrateRootfor generated markup, and SPA navigation after hydration. - Keep
en-UScanonical without a prefix. Publish/index any of the nine supported locales only when its visible and SEO content is fully translated with placeholder parity. - Treat route slugs as stable identifiers. They need not be English and MUST NOT vary by locale; slug changes require redirects and canonical planning.
- Keep route/page code in its bounded context and shared code behind a demonstrated cross-context consumer.
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 · 166 lines · 0 tokens per session scan A c2ec968cff4b
react-query-request-hooks 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 2,366 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
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.