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/solver-searchgit 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/instructions/williamisnotdefined/rubiks-cube-solver/solver-search)<a href="https://agentmods.dev/instructions/williamisnotdefined/rubiks-cube-solver/solver-search"><img src="https://agentmods.dev/badge/instructions/williamisnotdefined/rubiks-cube-solver/solver-search.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 | $0.02961 | $0.02961 |
| Opus 5 | $0.01481 | $0.01481 |
| Sonnet 5 | $0.00592 | $0.00592 |
| Haiku 4.5 | $0.00296 | $0.00296 |
Grade A, and why
rubiks-cube-solver solver-search.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 3d 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 — 290 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/solver-search.md.
Referenced context:
../../ai/rules/solver-search-rules.md../../ai/rules/testing-rules.md../../ai/architecture/project-architecture.md../../ai/architecture/solver-search.md../../ai/architecture/cube-engine.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: solver-search
Canonical Skill: ai/skills/solver-search.md
Solver Search
Use this skill when adding or changing IDA*, generated two-phase search, heuristics, pruning, or pattern database code.
Goal
Add search behavior only on top of correct cube state and move semantics.
Read First
ai/rules/solver-search-rules.mdai/rules/testing-rules.mdai/architecture/project-architecture.mdai/architecture/solver-search.mdai/architecture/cube-engine.mdai/glossary/cube-terms.md
Workflow
- Verify cube move behavior before trusting search results.
- Start with shallow deterministic cases.
- Keep heuristics separate from traversal logic.
- Mark whether each heuristic is admissible.
- Add node/depth metrics for non-trivial algorithms.
Expected Output
- Search returns explicit move sequences and metrics.
- Tests cover solved state and shallow known scrambles.
- No learned or external inference heuristic is introduced without an explicit current product requirement.
Verification
- Run
cargo test -p cube-enginewhen Rust is installed. - Include targeted tests for the changed search module.
Referenced Context
Reference: ai/rules/solver-search-rules.md
Solver Search Rules
Rules for search, heuristics, and pattern database work.
Always
- Keep search algorithms in
crates/cube-engine/src/searchunless a later crate boundary is introduced. - Keep heuristics explicit about admissibility.
- Prefer bounded IDA* and generated two-phase paths after move tables are correct.
- Prune inverse moves and repeated same-axis branches where correctness allows it.
- Measure node counts and depth limits for non-trivial search changes.
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.
- 3d ago First seen · 290 lines · 2,961 tokens per session scan A 4c875aa68701
rubiks-cube-solver solver-search.instructions.md is an instructions file published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 10d ago), licensed MIT. It adds 2,961 tokens to every session, about $0.0148 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
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
chroma AGENTS.md
AGENTS.md instructions for chroma-core/chroma: See CLAUDE.md for codebase conventions (commit message format, etc.).
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
terminal-browser AGENTS.md
AGENTS.md instructions for zenbu-labs/terminal-browser, a project described as: A browser inside your terminal.