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/project-core)<a href="https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/project-core"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/project-core/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/project-core"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/project-core.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.04510 | $0.04510 |
| Opus 5.5 | $0.01804 | $0.01804 |
| Sonnet 5.5 | $0.00902 | $0.00902 |
| Haiku 4.5 | $0.00451 | $0.00451 |
Grade A, and why
project-core 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 — 354 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/project-core.md.
Referenced context:
../../ai/rules/repository-rules.md../../ai/rules/testing-rules.md../../ai/rules/ai-rules.md../../ai/architecture/project-architecture.md../../ai/architecture/ai-knowledge-system.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: project-core
Canonical Skill: ai/skills/project-core.md
Project Core
Use this skill as the always-on repository baseline for AI-assisted changes anywhere in the Rubik's Cube solver.
Goal
Keep every change aligned with Rust engine boundaries, cube domain language, current project priorities, verification flow, and AI knowledge maintenance rules.
Read First
ai/rules/repository-rules.mdai/rules/testing-rules.mdai/rules/ai-rules.mdai/architecture/project-architecture.mdai/architecture/ai-knowledge-system.mdai/glossary/cube-terms.md
Workflow
- Start from
docs/project-plan.md, nearby code, tests, and source docs before changing behavior. - Create or switch to a dedicated task branch before changing files; never work or commit directly on
main. - Apply a narrower skill when the task touches cube engine, solver search, API boundary, frontend visualization, or AI knowledge.
- Keep solver logic in Rust and keep AI routes generated.
- Run targeted verification first, then broader checks when a change crosses boundaries.
Expected Output
- Code follows the current repository boundaries and documented priorities.
- Generated AI route files are never edited manually.
- Final reporting names verification that was run or explains why it was blocked.
Verification
- Run
npm run ai:checkafter AI knowledge changes. - Run
cargo test -p cube-engineafter engine changes when Rust is installed.
Referenced Context
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 · 354 lines · 4,510 tokens per session scan A d4727d7dc3c1
project-core is a cursor rule published in the GitHub repository williamisnotdefined/rubiks-cube-solver (5 stars, last pushed 4d ago), licensed MIT. It adds 4,510 tokens to every session, about $0.0180 per session on Opus 5.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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.