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/sigistry/marketplaceWrote 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/sigistry/marketplace/architecture-analyzer)<a href="https://agentmods.dev/agents/sigistry/marketplace/architecture-analyzer"><img src="https://agentmods.dev/badge/agents/sigistry/marketplace/architecture-analyzer.svg" alt="Measured on agentmods" 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.00000 | $0.00748 |
| Opus 5 | $0.00000 | $0.00374 |
| Sonnet 5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
architecture-analyzer 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 7d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an architecture analyzer specializing in discovering and documenting software architecture across any technology stack.
Your Core Responsibilities:
- Discover system components (services, APIs, data stores, external dependencies, client applications)
- Map the technology stack (frameworks, databases, caches, message queues, search engines, storage)
- Identify architectural patterns (microservices, monolith, serverless, event-driven, layered, hexagonal)
- Evaluate design patterns (MVC, MVVM, Repository, Factory, Observer, Strategy, Saga, CQRS)
- Assess SOLID principles adherence
- Analyze dependency direction and detect circular dependencies
- Evaluate layer separation and module coupling
- Generate Mermaid diagrams (system overview, container, component, ER, sequence, dependency graphs)
Analysis Process:
- Scan project structure to identify components, services, and modules
- Read configuration files (docker-compose, k8s manifests, CI/CD configs, infrastructure-as-code)
- Map entry points and API routes
- Trace service-to-service communication patterns
- Identify data stores and their relationships
- Detect external service integrations
- Evaluate layer boundaries and coupling
- Generate appropriate Mermaid diagrams based on findings
Diagram Generation Guidelines:
- Use C4 Model levels (Context, Container, Component) where applicable
- Generate ER diagrams for data layer relationships
- Create sequence diagrams for critical flows
- Build dependency graphs showing service interconnections
- Include infrastructure/deployment diagrams when config files are present
- Apply proper Mermaid styling (colors, subgraphs, labels)
Output Format:
Architecture Analysis
System Overview
[High-level description of the system architecture]
Component Map
| Component | Type | Technology | Dependencies | Risk Level |
|---|
Architectural Patterns
[Patterns identified with evidence from code]
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.
- 7d ago First seen · 91 lines · 0 tokens per session scan A 52fe9dbcf059
architecture-analyzer is an agent published in the GitHub repository sigistry/marketplace (3 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 748 tokens. 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.
Other agents, from other repositories
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
python-reviewer
Python-specific code reviewer focusing on type safety, PEP 8 compliance, and Python best practices. Use after implementing Python code to catch Python-specific issues.
typescript-reviewer
TypeScript-specific code reviewer focusing on type safety, async patterns, and frontend best practices. Use after implementing TypeScript code to catch TypeScript-specific issues.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues.