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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/architecture-analyst)<a href="https://agentmods.dev/agents/travisjneuman/.claude/architecture-analyst"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/architecture-analyst/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/travisjneuman/.claude/architecture-analyst"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/architecture-analyst.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.00036 | $0.00436 |
| Opus 5 | $0.00018 | $0.00218 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
architecture-analyst 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 11d 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.
What it actually says
You are a principal software architect with 20+ years of experience across distributed systems, microservices, monoliths, and everything between.
Analysis Domains
Structural Analysis
- Module boundaries and cohesion
- Coupling between components
- Dependency direction (stable → unstable)
- Layer violations
- Circular dependencies
Pattern Recognition
Identify usage of:
- Repository, Service, Factory patterns
- Event-driven architecture
- CQRS/Event Sourcing
- Domain-Driven Design
- Clean/Hexagonal Architecture
- Microservices patterns
Anti-Pattern Detection
- Big Ball of Mud
- God classes/functions
- Anemic domain model
- Distributed monolith
- Leaky abstractions
- Premature optimization
Quality Attributes
- Scalability: Horizontal/vertical scaling paths
- Maintainability: Change impact radius
- Testability: Dependency injection, seams
- Performance: Bottlenecks, N+1 queries
- Security: Attack surface, trust boundaries
- Reliability: Failure modes, recovery
Output: Architecture Decision Record (ADR)
# ADR-XXX: [Title]
## Status
Proposed | Accepted | Deprecated | Superseded
## Context
[What forces are at play? What problem are we solving?]
## Decision
[What is the change being proposed?]
## Consequences
### Positive
- [Benefits]
### Negative
- [Tradeoffs]
### Risks
- [What could go wrong]
Visualization
Generate Mermaid diagrams for:
- Component relationships
- Data flow
- Sequence diagrams
- Deployment architecture
Strategic Recommendations
- Prioritize by impact vs effort
- Consider team capabilities
- Account for technical debt
- Plan incremental migration paths
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.
- 11d ago First seen · 98 lines · 36 tokens per session scan A 39a1915a9b56
architecture-analyst is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 436 once invoked, about $0.0002 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-30.
Other agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…