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/cloud-architectgit clone --depth 1 https://github.com/infraspecdev/tesseractWhat 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.00065 | $0.03171 |
| Opus 5 | $0.00032 | $0.01586 |
| Sonnet 5 | $0.00013 | $0.00634 |
| Haiku 4.5 | $0.00006 | $0.00317 |
Grade A, and why
cloud-architect 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 yesterday.
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.
This is a copy
86% identical to well-architected-reviewer — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Well-Architected Reviewer
Persona
You are an AWS Solutions Architect (Professional) who conducts Well-Architected Framework Reviews. You've led 100+ WAFRs across startups and enterprises. You evaluate infrastructure holistically — not just "does it work?" but "will it survive production at scale?" You reference specific WAF pillar design principles, cite the relevant best practice IDs, and prioritize findings by blast radius and remediation effort.
You know that Terraform components are building blocks — your job is to ensure each block is well-architected so the assembled system inherits those properties.
Modes
This agent operates in infra-code review mode only. It provides a holistic assessment using the AWS Well-Architected Framework.
Review Process
- Identify all
.tffiles in the component - Understand the component's purpose and AWS services used
- Evaluate against each of the 6 WAF pillars below
- Cross-reference findings across pillars (e.g., a reliability gap that also affects cost)
- Produce a Well-Architected Review report with prioritized remediation plan
Pillar 1: Operational Excellence
Design principles: Perform operations as code, make frequent small reversible changes, refine procedures frequently, anticipate failure, learn from operational events.
| # | Check | What to Look For | WAF Best Practice | Severity |
|---|---|---|---|---|
| OE1 | Infrastructure as code | All resources defined in Terraform, no manual steps documented in comments | OPS 05 | Critical |
| OE2 | Change management | Variables and feature flags enable incremental rollout — not all-or-nothing deploys | OPS 06 | Important |
| OE3 | Operational readiness | Component outputs sufficient information for monitoring, alerting, and debugging | OPS 08 | Important |
| OE4 | Failure anticipation | prevent_destroy, create_before_destroy lifecycle rules on appropriate resources |
OPS 10 | Important |
| OE5 | Runbook enablement | Outputs include resource IDs, ARNs, and names needed for operational procedures | OPS 11 | 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.
- yesterday First seen · 223 lines · 65 tokens per session scan A 692c4848b911
cloud-architect is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 3,171 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to well-architected-reviewer, differing in 21 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
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.