agentmods.dev

architecture-review

architecture-review is a skill for Claude Code from cenconq25/claude-code-app-studio. It costs 69 tokens per session (1,918 once invoked), scanned A, original, MIT.

A read-only check that compares product-requirement documents with architecture decision records, which explain important technical choices. It produces a traceability matrix showing which requirements are covered and a PASS, CONCERNS, or FAIL verdict.

In plain words
What is it for?
Use it after the required architecture decisions are written, when requirements change, before the first sprint, or before a major release.
Why use it?
It exposes missing requirements, conflicting technical decisions, and architecture rules that have been overlooked before development or release.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

not rated 42repo 5mo ago A scan 69 tokens original MIT

Good fit Use it after the required architecture decisions are written, when requirements change, before the first sprint, or before a major release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cenconq25/claude-code-app-studio/architecture-review
View source ↗ cenconq25/claude-code-app-studio
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.

Any agent
npx skills add cenconq25/claude-code-app-studio --skill architecture-review
Clone the repo
git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

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 architecture-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/architecture-review/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/architecture-review)
Your own site
<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.

agentmods 80×15 button for architecture-review

Your own site · 80×15
<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>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00069 $0.01918
Opus 5.5 $0.00028 $0.00767
Sonnet 5.5 $0.00014 $0.00384
Haiku 4.5 $0.00007 $0.00192

Measured 1mo ago against content hash 3914c7758cdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.claude/skills/architecture-review/SKILL.md · 223 lines

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.md
  • docs/framework-reference/<framework>/
  • docs/architecture/architecture-registry.yaml if present

Outputs

  • A printed report including a traceability matrix and verdict
  • No file writes

Phase 1: Pre-checks

  • Confirm docs/architecture/architecture.md exists. Fail otherwise.
  • Confirm at least 1 ADR with Status: Accepted exists. 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:

  1. Extract all TR-IDs from Section 3 Detailed Requirements (TR-<system>-NNN)
  2. Identify which ADRs reference each TR-ID by grepping docs/architecture/ADR-*.md for 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

Read the full file on GitHub · 223 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. 1mo ago First seen · 223 lines · 69 tokens per session scan A 3914c7758cdb

Subscribe to this mod's changes

architecture-review is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 69 tokens to every session and 1,918 once invoked, about $0.0003 per session on Opus 5.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.

Building agentsPlanning
Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 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

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens