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/commands/juanmhidalgo/claude-plugins/architecture)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/architecture"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/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.
<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/architecture"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/architecture.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.00037 | $0.01179 |
| Opus 5.5 | $0.00015 | $0.00472 |
| Sonnet 5.5 | $0.00007 | $0.00236 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
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 14d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Overview
Generate a high-level architecture map of this project.
Arguments: $ARGUMENTS
Phase 0: Output Format
If $ARGUMENTS names ascii or html, use it. Otherwise ask once with AskUserQuestion:
- ASCII (default) — the overview below, in the terminal
- HTML page — the same overview as a standalone page with a rendered diagram, written to a file and opened in the browser
Phase 1: Discovery
- Layers - What are the main layers? (UI, API, services, data)
- Components - Major modules or packages
- Boundaries - How are components separated? (folders, packages, services)
- Communication - How do components talk to each other?
- External dependencies - Third-party services, databases, APIs
- Configuration - How is the system configured?
Phase 2: Generate Architecture Map
<output_format>
# Architecture Overview
## System Type
[Monolith | Modular Monolith | Microservices | Serverless | etc.]
## High-Level Diagram (ASCII)
┌─────────────────────────────────────────┐ │ Client │ └─────────────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────┐ │ API Layer │ │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ │ │ Routes │ │ Auth │ │ ... │ │ │ └─────────┘ └─────────┘ └─────────┘ │ └─────────────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────┐ │ Service Layer │ └─────────────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────┐ │ Data Layer │ └─────────────────────────────────────────┘
## Component Breakdown
### [Component 1]
- **Location**: `path/to/component/`
- **Responsibility**: What it does
- **Key files**: `file1.py`, `file2.py`
- **Depends on**: [Other components]
- **Depended by**: [Components that use this]
### [Component 2]
...
## Data Flow
### [Flow 1: User Authentication]
1. Request arrives at `routes/auth.py:login`
2. Validated by `services/auth.py:authenticate`
3. Token generated by `utils/jwt.py:create_token`
4. Response sent
### [Flow 2: ...]
...
## External Dependencies
| Service | Purpose | Config Location |
|---------|---------|-----------------|
| PostgreSQL | Primary database | `config/database.py` |
| Redis | Caching | `config/cache.py` |
## Key Patterns Used
| Pattern | Where Used | Example |
|---------|------------|---------|
| Repository | Data access | `repositories/user.py` |
| Service Layer | Business logic | `services/` |
## Areas of Complexity
- [Area 1]: Why it's complex, where to look
- [Area 2]: Why it's complex, where to look
</output_format>
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.
- 14d ago Changed · +27 lines 1a13a308a8be
- 1mo ago First seen · 127 lines · 37 tokens per session scan A 5aaf9de0bbe9
architecture is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,179 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 commands, from other repositories
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
setup-vercel.es
Command "setup-vercel.es" from minicoohei/ai-agent-camp, covering configuración de vercel cli, step 0: verificar progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: crear cuenta de vercel.