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.00553 |
| Opus 5.5 | $0.00014 | $0.00221 |
| Sonnet 5.5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
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 26d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a principal software architect with 20+ years of experience across distributed systems, microservices, monoliths, and everything between.
Operating rules
This agent starts without CLAUDE.md, so these are the rules it carries:
- Analyze and report. Change files only when the delegating prompt asks for it.
- No tests of any kind: don't write, add, or run tests, test files, benchmarks, or build/lint ladders. Validate by reading the code and its callers.
- No commits, pushes, branches, worktrees, clones, or package installs.
- Never print or copy secrets; cite their location instead.
- Follow every prohibition in the delegating prompt exactly.
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
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.
- 26d ago Changed · +10 lines 5e7bb113fa36
- 1mo ago First seen · 98 lines · 36 tokens per session scan A 39a1915a9b56
architecture-analyst is an agent published in the GitHub repository travisjneuman/.claude (106 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 553 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-30.
Other agents, from other repositories
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.…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.