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 skills add cenconq25/claude-code-app-studio --skill consistency-checkgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/consistency-check)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/consistency-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/consistency-check.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.00061 | $0.01794 |
| Opus 5 | $0.00030 | $0.00897 |
| Sonnet 5 | $0.00012 | $0.00359 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
consistency-check 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consistency Check
Compares what each PRD claims about shared entities, values, and formulas against the registry. Pure read — never writes a file. Produces a structured findings list the user can resolve with /design-system retrofit ... or /propagate-design-change.
Purpose / When to Run
Run when:
- Three or more PRDs exist
- A PRD has just been authored that overlaps with prior PRDs
- Before
/review-all-prds(which is more expensive)
Distinct from /review-all-prds: this skill checks values for drift; the holistic review checks design intent for contradictions. Run consistency-check first — it is much cheaper.
Inputs
design/registry/entities.yaml- All
design/prd/*.md - Optional:
design/systems-index.md
Outputs
- Printed findings. No file writes.
Phase 1: Load the Registry
Read design/registry/entities.yaml. The registry is the source of truth for cross-PRD facts. Each entry has:
nametype(entity / configurable / formula / constant / event / endpoint)valueorattributessource(the PRD that owns the canonical definition)referenced_by(other PRDs that reference it)
If the registry does not exist, stop:
"No
design/registry/entities.yamlfound. The registry is built incrementally as/design-systemruns. Cannot consistency-check without it. Either author more PRDs or run/design-system retrofit ...to populate the registry from existing PRDs."
If the registry has fewer than 5 entries, warn that meaningful checks need ≥5 entries — the skill will run but findings will be sparse.
Phase 2: Index Every PRD
For each design/prd/*.md:
- Read the file.
- Identify which registry entries it references — grep for each entry's
namein the file body. - For each referenced entry, extract the value the PRD claims (from sections 3 Detailed Requirements, 6 Configurable Values, and any inline tables).
Build a per-entry table:
entry: rate_limit_login_attempts
registry value: 5 (per minute)
source: design/prd/auth.md
referenced in:
design/prd/auth.md → 5 per minute ✓
design/prd/account-recovery.md → 3 per minute ✗ MISMATCH
design/prd/security.md → "5 attempts" ✓
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 · 199 lines · 61 tokens per session scan A ea6d7d826275
consistency-check is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,794 once invoked, about $0.0003 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-09-03.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…