project-core

project-core is a skill for Claude Code, Codex from williamisnotdefined/rubiks-cube-solver. It costs 19 tokens per session (4,505 once invoked), scanned A, original, MIT.

A repository-wide set of rules for keeping code changes within the project's boundaries, following the right instruction priority, checking the work, and maintaining the project's AI guidance. The repository is the project's code and related files.

In plain words
What is it for?
Use it for changes anywhere in the Rubik's Cube solver, especially when deciding where code belongs, which project guidance applies, and how to verify the result.
Why use it?
It gives coding tasks a shared baseline for architecture, testing, project priorities, and updates to the project's knowledge files.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/williamisnotdefined/rubiks-cube-solver/project-core
Any agent
npx skills add williamisnotdefined/rubiks-cube-solver --skill project-core
Clone the repo
git clone --depth 1 https://github.com/williamisnotdefined/rubiks-cube-solver

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for project-core

README.md
[![agentmods](https://agentmods.dev/badge/skills/williamisnotdefined/rubiks-cube-solver/project-core.svg)](https://agentmods.dev/skills/williamisnotdefined/rubiks-cube-solver/project-core)
Your own site
<a href="https://agentmods.dev/skills/williamisnotdefined/rubiks-cube-solver/project-core"><img src="https://agentmods.dev/badge/skills/williamisnotdefined/rubiks-cube-solver/project-core.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,505 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.04505
Opus 5 $0.00010 $0.02253
Sonnet 5 $0.00004 $0.00901
Haiku 4.5 $0.00002 $0.00451

Measured 5d ago against content hash a554dbeadef2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 5d 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.

.agents/skills/project-core/SKILL.md · 353 lines

How it starts

The opening of the file, as written. The whole thing — 353 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.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

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:check after AI knowledge changes.
  • Run cargo test -p cube-engine after engine changes when Rust is installed.

Read the full file on GitHub · 353 lines

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.

  1. 5d ago First seen · 353 lines · 19 tokens per session scan A a554dbeadef2

Subscribe to this mod's changes

project-core is a skill published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 11d ago), licensed MIT. It adds 19 tokens to every session and 4,505 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens