agentmods.dev

review-architecture

review-architecture is a skill for Claude Code, Codex from pilotspace/pilot-space. It costs 27 tokens per session (1,239 once invoked), scanned A, original, Apache-2.0.

An architecture review tool that examines a system design, including its components, data flows, data model, integrations, and related project decisions. Architecture is the high-level plan for how a software system is organized and works.

In plain words
What is it for?
Use it to review diagrams and written designs, check component boundaries and data relationships, assess external dependencies, and record findings for stakeholders.
Why use it?
It helps reveal design gaps, likely bottlenecks, scaling concerns, and mismatches with existing project decisions before implementation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: model in frontmatter.

not rated 2repo 4mo ago A scan 27 tokens original Apache-2.0

Good fit Use it to review diagrams and written designs, check component boundaries and data relationships, assess external dependencies, and record findings for stakeholders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pilotspace/pilot-space/review-architecture
View source ↗ pilotspace/pilot-space
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 pilotspace/pilot-space --skill review-architecture
Clone the repo
git clone --depth 1 https://github.com/pilotspace/pilot-space

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/pilotspace/pilot-space/review-architecture/github.svg)](https://agentmods.dev/skills/pilotspace/pilot-space/review-architecture)
Your own site
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/review-architecture"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/review-architecture/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 review-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/review-architecture"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/review-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,239 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.00027 $0.01239
Opus 5.5 $0.00011 $0.00496
Sonnet 5.5 $0.00005 $0.00248
Haiku 4.5 $0.00003 $0.00124

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

Security

Grade A, and why

review-architecture 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 2mo 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.

backend/src/pilot_space/ai/templates/skills/review-architecture/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Architecture Skill

Perform a senior architect-level review of system architecture described in a note. Analyzes component design, data flows, scalability patterns, and alignment with project design decisions. Writes structured findings to a PM block for stakeholder review.

Quick Start

Use this skill when:

  • User requests an architecture review (/review-architecture)
  • Agent detects architecture diagrams or system design in note content
  • User asks "is this design good?" or "what are the risks here?"

Example:

User: "Review the architecture for our new notification system"

AI reviews:
- Component boundaries: Are responsibilities well-separated?
- Scalability: What's the bottleneck at 10k users?
- Data model: Correct relationship cardinality? Index strategy?
- Integration points: External dependencies, circuit breakers?
- Alignment: Does this follow DD-001 (async-first) and DD-064 (CQRS-lite)?

Workflow

  1. Parse Architecture Description

    • Read all content from note (diagrams, prose, component lists, data models)
    • Use search_notes to find related architecture decisions or existing components
    • Use get_project to understand project scope and tech stack constraints

  2. Analyze Architecture Dimensions

    • Component Design: SRP violations, God classes, missing abstractions
    • Data Model: Normalization, relationship cardinality, index coverage, N+1 risks
    • Scalability: Bottlenecks, stateful components, horizontal scaling barriers
    • Resilience: Single points of failure, missing circuit breakers, timeout strategy
    • Security: Auth boundaries, data isolation, RLS enforcement plan
    • Design Alignment: DD-001 (async-first), DD-003 (approval), DD-064 (CQRS), DD-086 (centralized agent)

  3. Classify Findings

    • BLOCKER: Fundamental design flaw — must fix before implementation
    • HIGH: Scalability or security risk — fix in sprint before ship
    • MEDIUM: Technical debt — plan for next sprint
    • LOW: Optional improvement — backlog item

Read the full file on GitHub · 130 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. 2mo ago First seen · 130 lines · 27 tokens per session scan A 4a67fe2b8c1c

Subscribe to this mod's changes

review-architecture is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,239 once invoked, about $0.0001 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-31.

Planning
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

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…

vercel/next.js · 83 tokens