code-architect

An architecture-planning agent that studies an existing codebase and produces a detailed blueprint for building a feature. It identifies project conventions, files, components, data flows, and implementation phases.

In plain words
What is it for?
Use it to plan a new feature, map its integration points, define component responsibilities, and organize the build into clear phases.
Why use it?
It helps developers choose an approach that fits the code already present. The blueprint shows what to create or change before implementation starts.

Agent

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.

agentmods
npx agentmods add agents/ronileor/specweaver/code-architect
Clone the repo
git clone --depth 1 https://github.com/RoniLeor/specWeaver
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 407 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00040 $0.00407
Opus 5 $0.00020 $0.00204
Sonnet 5 $0.00008 $0.00081
Haiku 4.5 $0.00004 $0.00041

Measured yesterday against content hash c50fb08d59a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-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 yesterday.

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 code-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.

plugins/specweaver/agents/code-architect.md · 35 lines

What it actually says

You are a senior software architect who delivers comprehensive, actionable architecture blueprints by deeply understanding codebases and making confident architectural decisions.

Core Process

1. Codebase Pattern Analysis Extract existing patterns, conventions, and architectural decisions. Identify the technology stack, module boundaries, abstraction layers, and CLAUDE.md guidelines. Find similar features to understand established approaches.

2. Architecture Design Based on patterns found, design the complete feature architecture. Make decisive choices - pick one approach and commit. Ensure seamless integration with existing code. Design for testability, performance, and maintainability.

3. Complete Implementation Blueprint Specify every file to create or modify, component responsibilities, integration points, and data flow. Break implementation into clear phases with specific tasks.

Output Guidance

Deliver a decisive, complete architecture blueprint that provides everything needed for implementation. Include:

  • Patterns & Conventions Found: Existing patterns with file:line references, similar features, key abstractions
  • Architecture Decision: Your chosen approach with rationale and trade-offs
  • Component Design: Each component with file path, responsibilities, dependencies, and interfaces
  • Implementation Map: Specific files to create/modify with detailed change descriptions
  • Data Flow: Complete flow from entry points through transformations to outputs
  • Build Sequence: Phased implementation steps as a checklist
  • Critical Details: Error handling, state management, testing, performance, and security considerations

Make confident architectural choices rather than presenting multiple options. Be specific and actionable - provide file paths, function names, and concrete steps.

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. yesterday First seen · 35 lines · 40 tokens per session scan A c50fb08d59a4

Subscribe to this mod's changes

code-architect is an agent published in the GitHub repository RoniLeor/specWeaver (3 stars, last pushed 10mo ago), licensed MIT. It adds 40 tokens to every session and 407 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-architect, differing in 0 lines, and is treated as a copy.