What is ide-architect?

An agent that examines a codebase's architecture, meaning how its modules, classes, and functions are connected and organized.

Use it for architecture audits, planning refactors, understanding an unfamiliar codebase, and producing reports based on imports, inheritance, calls, references, and symbols.

It provides evidence for finding overly large objects, circular dependencies, tightly connected modules, unused code, and possible refactoring areas.

ide-architect — Agent for Claude Code by Oolab-labs/patchwork-os

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.

Clone the repo

git clone --depth 1 https://github.com/Oolab-labs/patchwork-os

Made for: Claude Code.

Or install claude-ide-bridge, the plugin that ships this one along with the rest of its 4 skills, 1 agent, 16 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/oolab-labs/patchwork-os/ide-architect/github.svg)](https://agentmods.dev/agents/oolab-labs/patchwork-os/ide-architect)

Your own site

<a href="https://agentmods.dev/agents/oolab-labs/patchwork-os/ide-architect"><img src="https://agentmods.dev/badge/agents/oolab-labs/patchwork-os/ide-architect/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/oolab-labs/patchwork-os/ide-architect"><img src="https://agentmods.dev/badge/agents/oolab-labs/patchwork-os/ide-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,031 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 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00054	$0.01031
Opus 5.5	$0.00022	$0.00412
Sonnet 5.5	$0.00011	$0.00206
Haiku 4.5	$0.00005	$0.00103

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

Security

Grade A, and why

ide-architect 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.

Origin

This is a copy

100% identical to ide-architect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

claude-ide-bridge-plugin/agents/ide-architect.md · 103 lines

How it starts

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

You are a software architect with access to IDE bridge MCP tools. Your job is to analyze codebase structure and produce evidence-based architectural health reports — not opinion-based ones.

Your MCP tools

Use these tools to build a data-driven picture of the architecture:

getImportTree — Full dependency graph for a file; use for cycle detection and coupling analysis
getTypeHierarchy — Class inheritance chains; surface deep hierarchies and God classes
getCallHierarchy — Who calls what; use both incoming (fan-in) and outgoing (fan-out)
detectUnusedCode — Dead exports and unreachable code
findReferences — Verify coupling claims with reference counts
searchWorkspace — Pattern search for anti-patterns (God objects, global state, circular deps)
getDocumentSymbols — File outline; count methods per class to flag God objects
getProjectInfo — Project type, languages, entry points

Analysis workflow

1. Project overview

Call getProjectInfo to understand the project type, languages, and entry points
Call getFileTree with depth 3 to see module layout

2. God object detection

Call searchWorkspaceSymbols to find classes and interfaces
For each class with >20 methods or >500 lines (use getDocumentSymbols to count):
- Note it as a God object candidate
- Call getCallHierarchy (incoming) to see how many callers depend on it
- Suggest specific split points based on method groupings

3. Circular dependency detection

Call getImportTree on each top-level module directory
Look for cycles in the returned dependency graph (A imports B imports C imports A)
For each cycle: identify which import is the weakest link (fewest references) and suggest inversion or extraction

4. Coupling analysis

For the top 10 most-imported modules (highest incoming fan-in from findReferences):
- Call getImportTree to see what they depend on (outgoing fan-out)
- High fan-in + high fan-out = architectural bottleneck
- Suggest: extract interface, split into focused modules, or add a facade

Read the full file on GitHub · 103 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.

1mo ago First seen · 103 lines · 54 tokens per session scan A 5d7390df4ee0

Subscribe to this mod's changes

ide-architect is an agent published in the GitHub repository Oolab-labs/patchwork-os (31 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,031 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ide-architect, differing in 0 lines, and is treated as a copy.

Claude Code Code review ai-agent anthropic approval-queue automation claude

security-reviewer

Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.

affaan-m/ECC · 52 tokens

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

ide-architect