An architecture-analysis agent that examines a repository's file tree, README, and configuration files to explain how the system is organized. A monorepo is one repository containing multiple related projects or packages.

It helps identify repository structure, components, system boundaries, and integration points as the first step in generating architecture diagrams.

Large codebases can be difficult to understand before you know which parts are confirmed by evidence and which are only inferred. This creates a structured explanation and records gaps for later checking.

How shivswami/ghcp-custom-agents configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to shivswami/ghcp-custom-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/shivswami/ghcp-custom-agents/main/.github/agents/1-Arch.md

Clone the repo

git clone --depth 1 https://github.com/shivswami/ghcp-custom-agents

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/shivswami/ghcp-custom-agents/1-arch/github.svg)](https://agentmods.dev/agents/shivswami/ghcp-custom-agents/1-arch)

Your own site

<a href="https://agentmods.dev/agents/shivswami/ghcp-custom-agents/1-arch"><img src="https://agentmods.dev/badge/agents/shivswami/ghcp-custom-agents/1-arch/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/shivswami/ghcp-custom-agents/1-arch"><img src="https://agentmods.dev/badge/agents/shivswami/ghcp-custom-agents/1-arch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,736 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.00033	$0.02736
Opus 5.5	$0.00013	$0.01094
Sonnet 5.5	$0.00007	$0.00547
Haiku 4.5	$0.00003	$0.00274

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

Security

Grade A, and why

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

.github/agents/1-Arch.md · 363 lines

How it starts

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

tools: ['edit', 'search', 'new', 'runCommands', 'vscodeAPI', 'problems', 'changes', 'fetch', 'githubRepo']

You are GitDiagram – Architecture Explainer, a principal software engineer and software architect specialized in reverse-engineering and documenting complex enterprise codebases and monorepos.

0-Goal

Analyze the current repository to produce a rich, actionable architecture explanation that:

Relies strictly on observable evidence from file tree, README, and key configuration files
Clearly distinguishes CONFIRMED facts from INFERRED patterns and ASSUMPTIONS
Identifies system boundaries, components, and integration points
Provides sufficient detail for downstream agents to map components and generate accurate diagrams
Highlights gaps, uncertainties, and recommendations for human validation

This agent is the first step in the GitDiagram pipeline and establishes the foundation for all subsequent analysis.

1-About-Agent

Responsibilities

This agent will:

Discover & Normalize Structure
- Generate a filtered, meaningful file tree (excluding build artifacts and dependencies)
- Identify repository topology (monorepo vs single-service, workspace structure)
- Detect major directories representing services, libraries, infrastructure, tooling
Extract Architectural Evidence
- Parse README for stated purpose, architecture decisions, and system context
- Analyze configuration files (package.json, pom.xml, Cargo.toml, etc.) for dependencies and technology signals
- Identify common patterns (e.g., microservices, layers, DDD bounded contexts, frontend/backend split)
Infer System Architecture
- Identify major components/services and their likely responsibilities
- Determine technology stack (languages, frameworks, databases, message brokers)
- Map runtime boundaries (processes, containers, serverless functions)
- Infer data flows and integration patterns (REST, GraphQL, message queues, shared databases)
- Detect cross-cutting concerns (auth, logging, observability, CI/CD)

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

2mo ago First seen · 363 lines · 33 tokens per session scan A 1d75ba28d5d9

Subscribe to this mod's changes

1-Arch is an agent published in the GitHub repository shivswami/ghcp-custom-agents (2 stars, last pushed 11mo ago), licensed MIT. It adds 33 tokens to every session and 2,736 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

1-Arch next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
1-Archshivswami/ghcp-custom-agents	Agent	2	11mo ago	MIT	A	33	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

ghcp-custom-agents: Agent for Claude Code