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 architecture-reviewgit 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/architecture-review)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/architecture-review"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/architecture-review/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/skills/cenconq25/claude-code-app-studio/architecture-review"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/architecture-review.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.00069 | $0.01918 |
| Opus 5 | $0.00034 | $0.00959 |
| Sonnet 5 | $0.00014 | $0.00384 |
| Haiku 4.5 | $0.00007 | $0.00192 |
Grade A, and why
architecture-review 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 9d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Review
Holistic check that every PRD requirement is covered by an ADR, that ADRs do not contradict each other, that the framework knowledge-cutoff risk is honored across all decisions, and that no architectural stance is silently broken.
Read-only. Outputs a structured verdict and traceability matrix.
Purpose / When to Run
Run when:
- All P0 ADRs from the architecture's Required list are written
- A batch of PRDs changed (after
/propagate-design-change) - Before kicking off the first sprint
- Before a major release
Run in a fresh session — independent of any authoring context.
Inputs
docs/architecture/architecture.md- All
docs/architecture/ADR-*.md - All
design/prd/*.md design/systems-index.mddocs/framework-reference/<framework>/docs/architecture/architecture-registry.yamlif present
Outputs
- A printed report including a traceability matrix and verdict
- No file writes
Phase 1: Pre-checks
- Confirm
docs/architecture/architecture.mdexists. Fail otherwise. - Confirm at least 1 ADR with
Status: Acceptedexists. If none, run anyway but in degraded mode.
If running degraded, label the report header: "Degraded — no Accepted ADRs yet. This pass identifies coverage gaps only."
Phase 2: Build the Traceability Index
For each PRD:
- Extract all TR-IDs from Section 3 Detailed Requirements (
TR-<system>-NNN) - Identify which ADRs reference each TR-ID by grepping
docs/architecture/ADR-*.mdfor the TR-ID
Build a matrix:
| PRD | TR-ID | Requirement summary | Covered by | ADR Status |
|-----|-------|---------------------|------------|------------|
| auth.md | TR-auth-001 | OAuth login | ADR-0003 | Accepted |
| auth.md | TR-auth-002 | Token refresh | ADR-0003 | Accepted |
| auth.md | TR-auth-003 | Biometric unlock | — | UNCOVERED |
| paywall.md | TR-paywall-001 | Receipt validation | ADR-0009 | Proposed |
Categorize each row:
- COVERED — Accepted — TR-ID has at least one ADR with Status: Accepted addressing it
- COVERED — Proposed — TR-ID has an ADR but the ADR is still Proposed
- UNCOVERED — TR-ID has no ADR reference
- OVER-COVERED — TR-ID has multiple Accepted ADRs that may conflict
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.
- 9d ago First seen · 223 lines · 69 tokens per session scan A 3914c7758cdb
architecture-review is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 1,918 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-08-30.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…