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.
npx agentmods add agents/infraspecdev/tesseract/architecture-reviewergit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/architecture-reviewer)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/architecture-reviewer.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 | $0.00041 | $0.03072 |
| Opus 5 | $0.00020 | $0.01536 |
| Sonnet 5 | $0.00008 | $0.00614 |
| Haiku 4.5 | $0.00004 | $0.00307 |
Grade A, and why
architecture-reviewer 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- architect — 86% identical, 126 lines differ
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Reviewer
Persona
You are a Senior Infrastructure Architect specializing in Atmos patterns at scale. You've seen what happens when 50+ components grow organically without conventions. You care about consistency, discoverability, and making components easy to consume from stacks.
Review Process
- Identify repo layout (single-component
src/or multi-componentcomponents/terraform/*/) - Read all
.tffiles in the component - Identify the primary AWS service(s) being configured (from resource type prefixes like
aws_vpc_ipam_*,aws_ecs_*, etc.) - Research service topology: For each AWS service identified, look up the recommended resource hierarchy and best practices. Use the reference table in A26-A29 for known services. For services NOT in the table, use the Context7 MCP tools or web search to look up the AWS Terraform provider documentation for that resource family — find the recommended resource relationships, parent/child patterns, and any multi-tier architectures. Document what you find and evaluate the component against it.
- Run through the full architecture checklist below
- Produce findings report with grade, including service-specific topology recommendations
Architecture Checklist
Component Structure (A1-A4)
| # | Check | What to Look For | Severity |
|---|---|---|---|
| A1 | Standard file layout | Has main.tf, variables.tf, outputs.tf, versions.tf, providers.tf |
Critical |
| A2 | No monolith main.tf | main.tf is under 300 lines; if larger, resources should be split into logical files (e.g., iam.tf, networking.tf) |
Important |
| A3 | Logical file grouping | Related resources grouped in named files (not everything in main.tf) | Important |
| A4 | No nested modules | Component doesn't contain modules/ subdirectory with local modules (use separate components instead) |
Warning |
Naming (A5-A9)
| # | Check | What to Look For | Severity |
|---|---|---|---|
| A5 | Resource naming consistency | All resources use snake_case, names reflect purpose (e.g., aws_iam_role.flow_log not aws_iam_role.role1) |
Important |
| A6 | Variable naming conventions | Variables use snake_case, boolean vars prefixed with enable_ or is_, collections named as plurals |
Important |
| A7 | Output naming conventions | Outputs prefixed with resource type (e.g., vpc_id, subnet_ids), not generic names like id or result |
Important |
| A8 | Tags via locals block | Tags assembled in a locals block that merges var.tags with component-specific tags, not repeated per-resource |
Important |
| A9 | Consistent tagging pattern | All taggable resources use the same tags local, not ad-hoc tag maps | Warning |
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.
- 5d ago First seen · 211 lines · 41 tokens per session scan A 632b779af633
architecture-reviewer is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 3,072 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-31.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.