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 instructions/williamisnotdefined/rubiks-cube-solver/rust-module-refactorgit 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.03303 | $0.03303 |
| Opus 5 | $0.01651 | $0.01651 |
| Sonnet 5 | $0.00661 | $0.00661 |
| Haiku 4.5 | $0.00330 | $0.00330 |
Grade A, and why
rubiks-cube-solver rust-module-refactor.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 298 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.
- 2d ago First seen · 298 lines · 3,303 tokens per session scan A 045c00f0b6c8
rubiks-cube-solver rust-module-refactor.instructions.md is an instructions file published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 9d ago), licensed MIT. It adds 3,303 tokens to every session, about $0.0165 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 instructions, from other repositories
cli AGENTS.md
Instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
ton-rs AGENTS.md
Instructions for ston-fi/ton-rs, covering ton-rs agent guide, repository, boundaries, public api and ton invariants.
cli AGENTS.md
Instructions for rustfs/cli, covering agents.md - ai development guidelines, language requirements, first-principles reasoning, workflow and 0. branch base policy.