What is generate-architecture?

A repository analysis that creates an ARCHITECTURE.md file describing how the project is actually organized. This file gives AI coding assistants persistent guidance about where code belongs and how the system works.

Use it to inspect the directory structure, dependencies, framework, routing, state management, and testing setup, then document the observed architecture.

It reduces incorrect assumptions when an assistant changes a project it has not seen before.

generate-architecture — Agent for Claude Code by shuchitajain

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/shuchitajain/awesome-ai-setup

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/shuchitajain/awesome-ai-setup/generate-architecture/github.svg)](https://agentmods.dev/agents/shuchitajain/awesome-ai-setup/generate-architecture)

Your own site

<a href="https://agentmods.dev/agents/shuchitajain/awesome-ai-setup/generate-architecture"><img src="https://agentmods.dev/badge/agents/shuchitajain/awesome-ai-setup/generate-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/shuchitajain/awesome-ai-setup/generate-architecture"><img src="https://agentmods.dev/badge/agents/shuchitajain/awesome-ai-setup/generate-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 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,619 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.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.01619
Opus 5	$0.00012	$0.00809
Sonnet 5	$0.00005	$0.00324
Haiku 4.5	$0.00002	$0.00162

Measured 9d ago against content hash 58e1f484cb25, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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

agents/generate-architecture.md · 152 lines

How it starts

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

Generate ARCHITECTURE.md

You are generating an ARCHITECTURE.md file for this repository.

This file will be loaded as persistent context for AI coding assistants. Its job is to tell AI tools where things belong, how the system is organized, and what the rules are - before they write a single line of code.

Accuracy matters more than completeness. An incomplete file that is entirely correct is more useful than a comprehensive file with invented details.

Step 1 - Read the Repository

Before writing anything, gather information. Read these in order:

Top-level directory listing - understand the repo structure
Primary source directory (lib/, src/, app/, or equivalent) - list all subdirectories
Dependency manifest - read pubspec.yaml, package.json, Cargo.toml, go.mod, or equivalent. Note the state management, routing, DI, and testing libraries actually present.
Detect the primary framework version by running the appropriate command:
- Flutter → flutter --version (captures Flutter version, Dart version, and channel)
- Node.js / React / Next.js → node --version; read react, next, vue, svelte, or angular version from the manifest
- Rust → rustc --version
- Go → go version
- Python → python3 --version If the command fails or the tool is not on PATH, note "version unavailable" and continue.
Sample 4–6 files from different areas of the codebase:
- A file that manages state (store, provider, notifier, view model, reducer)
- A screen, view, or component file
- A data access file (repository, service, API client, data source)
- A domain/business logic file (use case, interactor, domain service) if present
- A test file
Router/navigation config if it exists as a separate file

Do not proceed to Step 2 until you have read actual code. Do not infer from dependency names alone.

Reference Example (Optional)

Check for a reference example in this order:

.ai/reference/*/ARCHITECTURE.md - if the user copied one during setup
node_modules/awesome-ai-setup/examples/*/ARCHITECTURE.md - if the package is installed locally

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

9d ago First seen · 152 lines · 24 tokens per session scan A 58e1f484cb25

Subscribe to this mod's changes

generate-architecture is an agent published in the GitHub repository shuchitajain/awesome-ai-setup (5 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,619 once invoked, about $0.0001 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-31.

Building agents ai ai-agents context-engineering github-copilot mcp

apm-expert

Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.

microsoft/apm · 39 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens

Prompt Builder

Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.

github/awesome-copilot · 24 tokens

PHP MCP Expert

Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.

github/awesome-copilot · 20 tokens

react18-class-surgeon

Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…

github/awesome-copilot · 81 tokens

Custom Agent Foundry

Expert at designing and creating VS Code custom agents with optimal configurations.

github/awesome-copilot · 17 tokens