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/rust-module-refactor)<a href="https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/rust-module-refactor"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/rust-module-refactor/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/rust-module-refactor"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/rust-module-refactor.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.03331 |
| Opus 5.5 | $0.00000 | $0.01332 |
| Sonnet 5.5 | $0.00000 | $0.00666 |
| Haiku 4.5 | $0.00000 | $0.00333 |
Grade A, and why
rust-module-refactor 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 — 300 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/rust-module-refactor.md.
Referenced context:
../../ai/rules/rust-module-refactor-rules.md../../ai/rules/testing-rules.md../../ai/architecture/project-architecture.md../../ai/architecture/rust-module-boundaries.md../../ai/glossary/cube-terms.md
This file is compiled from canonical AI knowledge files. Edit canonical files under ai, then run npm run ai:sync.
Compiled AI Skill: rust-module-refactor
Canonical Skill: ai/skills/rust-module-refactor.md
Rust Module Refactor
Use this skill when splitting large Rust files, changing mod.rs facades, moving tests, tightening visibility, or improving Rust module boundaries without changing behavior.
Goal
Make Rust code easier to read and maintain by extracting concrete responsibilities while preserving public API, solver behavior, artifact compatibility, and verification coverage.
Read First
ai/rules/rust-module-refactor-rules.mdai/rules/testing-rules.mdai/architecture/project-architecture.mdai/architecture/rust-module-boundaries.mdai/glossary/cube-terms.md
Related References
- Use
cube-enginewhen the refactor touches cube state, moves, notation, facelets, or validation. - Use
solver-searchwhen the refactor touches search, heuristics, pruning tables, or two-phase internals. - Use
api-boundarywhen the refactor touches Axum routes, request/response structs, or frontend-facing status contracts.
Workflow
- Identify the current public API and preserve it with facade modules and
pub usebefore moving implementation details. - Split one responsibility at a time: errors, config, result types, parsing, conversion, dispatch, table IO, search traversal, ordering, or tests.
- Prefer private modules and
pub(crate)exports unless an existing caller needs the item. - Keep mechanical moves separate from algorithm, heuristic, format, or contract changes.
- Move tests only when the new location makes the behavior owner clearer.
- Run targeted tests after each module family, then broader crate tests after a larger boundary is stable.
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 · 300 lines · 0 tokens per session scan A 245b50bfafa5
rust-module-refactor 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,331 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
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
arc-deref-pattern
When implementing parallel (Mt) algorithms in Verus, do NOT assume.
wrap-vs-specify
When to use externaltypespecification vs wrapper struct for Verus specs.
core
Core STT/TTS abstraction layer documentation.
spec-fn-naming
Spec function naming conventions.