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 skills/williamisnotdefined/rubiks-cube-solver/api-boundarynpx skills add williamisnotdefined/rubiks-cube-solver --skill api-boundarygit 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/skills/williamisnotdefined/rubiks-cube-solver/api-boundary)<a href="https://agentmods.dev/skills/williamisnotdefined/rubiks-cube-solver/api-boundary"><img src="https://agentmods.dev/badge/skills/williamisnotdefined/rubiks-cube-solver/api-boundary.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.00027 | $0.03003 |
| Opus 5 | $0.00014 | $0.01502 |
| Sonnet 5 | $0.00005 | $0.00601 |
| Haiku 4.5 | $0.00003 | $0.00300 |
Grade A, and why
api-boundary 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 4d 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 — 206 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/api-boundary.md.
Referenced context:
../../../ai/rules/api-rules.md../../../ai/rules/frontend-rules.md../../../ai/rules/testing-rules.md../../../ai/architecture/api-boundary.md
This file is compiled from canonical AI knowledge files. Edit canonical files under ai, then run npm run ai:sync.
Compiled AI Skill: api-boundary
Canonical Skill: ai/skills/api-boundary.md
API Boundary
Use for Axum routes, contracts, validation, solver loading, scan sessions, or the matching web API client.
Read First
ai/rules/api-rules.mdai/rules/frontend-rules.mdai/rules/testing-rules.mdai/architecture/api-boundary.md
Workflow
- Inspect the focused route/response/solve modules and matching client contract.
- Keep engine semantics in Rust, HTTP limits and status mapping in Axum, and normalization in the web API domain.
- Preserve typed scan stickers and the server-side 308 WCA docs redirect where affected.
- Run API tests plus web tests/build when the browser contract changes.
Referenced Context
Reference: ai/rules/api-rules.md
API Rules
Rules for the Axum HTTP API and the frontend API contract.
Always
- Keep route handlers thin: extract state and JSON, validate request limits, choose the solver strategy, delegate to Rust engine code, and map results to HTTP responses.
- Keep solver behavior in
cube-engine;crates/apiowns HTTP shape, safety limits, generated-solver loading, CORS, and error/status mapping. - Use Serde request and response structs as the API contract.
- Keep notation solve requests on move notation and route scan solves through typed scan-session contracts, which MAY include reviewed stickers and manual overrides.
- Validate API safety limits before parsing notation or invoking search.
- Use named constants for public API caps such as maximum depth, maximum nodes, notation bytes, and JSON body bytes.
- Preserve stable response status strings, error kinds, and metadata fields because
apps/web/src/apinormalizes them. - Verify returned solutions by replay before reporting success.
- Keep generated pruning-table availability and corruption errors explicit in API responses.
- Keep CORS origins narrow to known local web development and preview origins unless deployment requirements change.
- Update
apps/web/src/apitypes and normalization when API response fields or status values change. - Keep
/api/wca-dataas an Axum HTTP 308 redirect to/api/wca-data/v1/docs; WCA data endpoints belong toapps/wca-data.
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.
- 4d ago First seen · 206 lines · 27 tokens per session scan A 0cc353ef03b5
api-boundary is a skill published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 3,003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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.
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…