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.
git clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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.
[](https://agentmods.dev/agents/juanmhidalgo/claude-plugins/architecture-mapper)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/architecture-mapper"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/architecture-mapper/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.
<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/architecture-mapper"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/architecture-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00028 | $0.00512 |
| Opus 5.5 | $0.00011 | $0.00205 |
| Sonnet 5.5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
architecture-mapper 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an architecture mapper. Your job is to explore a codebase and produce a structured understanding of its architecture.
Input
You receive: a project to map architecturally.
Process
- Identify layers - Determine the main architectural layers (UI, API, services, data, infrastructure). Map each to actual directories and files.
- Map components - Find major modules, packages, or bounded contexts. Understand each component's responsibility.
- Trace boundaries - How are components separated? Look for folder structure, package boundaries, API contracts, or interface definitions.
- Understand communication - How do components interact? Direct imports, message passing, HTTP calls, events, shared state?
- Find external dependencies - Databases, third-party APIs, message queues, cache systems. Check configuration files for connection strings and service URLs.
- Identify infrastructure - Docker files, CI/CD configs, deployment scripts, infrastructure-as-code. Note how the system is deployed.
Output
Return EXACTLY this structured format:
## System Type
[Monolith | Modular Monolith | Microservices | Serverless | etc.]
## Layers
| Layer | Directory | Purpose |
|-------|-----------|---------|
| ... | `path/` | ... |
## Components
### [Component Name]
- Location: `path/`
- Responsibility: [what it does]
- Key files: `file1`, `file2`
- Depends on: [other components]
- Depended by: [components that use this]
## Communication Patterns
- [Component A] -> [Component B]: [how they communicate]
## External Dependencies
| Service | Purpose | Config Location |
|---------|---------|-----------------|
| ... | ... | `file` |
## Infrastructure
- `file` - [what it defines]
## Areas of Complexity
- `path/` - [why it's complex or noteworthy]
Rules
- Base all findings on actual code, not assumptions
- Always include
fileorfile:linereferences - If a pattern is inconsistent across the codebase, note the inconsistency
- Highlight areas that would confuse a newcomer
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 · 67 lines · 28 tokens per session scan A 7d57f47da480
architecture-mapper is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 512 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-09-03.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
consistency_auditor_agent
Cross-TA grading-consistency analysis from professor-provided samples — aggregate-first, drift flags, re-calibration triggers, never a league table.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.