Borrowing it
Nothing to install: this file belongs to williamisnotdefined/rubiks-cube-solver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/williamisnotdefined/rubiks-cube-solver/main/.agents/skills/wca-data-boundary/SKILL.mdgit 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/wca-data-boundary)<a href="https://agentmods.dev/skills/williamisnotdefined/rubiks-cube-solver/wca-data-boundary"><img src="https://agentmods.dev/badge/skills/williamisnotdefined/rubiks-cube-solver/wca-data-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.1 | $0.00031 | $0.02457 |
| Opus 5 | $0.00015 | $0.01229 |
| Sonnet 5 | $0.00006 | $0.00491 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
wca-data-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 7d 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 — 168 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/wca-data-boundary.md.
Referenced context:
../../../ai/rules/wca-data-rules.md../../../ai/rules/frontend-rules.md../../../ai/rules/testing-rules.md../../../ai/architecture/wca-data.md
This file is compiled from canonical AI knowledge files. Edit canonical files under ai, then run npm run ai:sync.
Compiled AI Skill: wca-data-boundary
Canonical Skill: ai/skills/wca-data-boundary.md
WCA Data Boundary
Use for the WCA Data workspace, OpenAPI contract, import worker, PostgreSQL lifecycle, or web WCA client.
Read First
ai/rules/wca-data-rules.mdai/rules/frontend-rules.mdai/rules/testing-rules.mdai/architecture/wca-data.md
Workflow
- Identify whether the change owns public API, canonical data, import, persistence, worker, or web consumption.
- Preserve contract-first OpenAPI and dataset metadata; keep Axum/Nginx routing aligned around the non-localized 308 docs redirect.
- Use fixture/disposable verification unless a real target was explicitly approved.
- Run WCA build/tests and the relevant web client tests; run public smoke only against an intentional available target.
Referenced Context
Reference: ai/rules/wca-data-rules.md
WCA Data Rules
- Treat
apps/wca-data/openapi/wca-data-v1.yamland contract tests as the public API contract. - Keep import, canonical domain, public API, persistence, and worker concerns separately owned.
- Validate archive size and expected entries; extract only expected TSV files.
- Run local write checks with
npm run wca:sync-once -- --fixture. Real sync and persistent migrations require explicit target approval. - Never execute downloaded SQL or expose fixture data in production. A successful production import retains only the active dataset; retired and failed datasets are removed after atomic publication, so rollback requires a backup or fresh verified import.
- Verify workspace changes with
npm run wca:buildandnpm run wca:test; use the public smoke command only when the target is intentional and available.
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.
- 7d ago First seen · 168 lines · 31 tokens per session scan A 8fdfb973f37c
wca-data-boundary is a skill published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 2,457 once invoked, about $0.0002 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…