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/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/operations-reviewer)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/operations-reviewer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/operations-reviewer/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/infraspecdev/tesseract/operations-reviewer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/operations-reviewer.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.01537 |
| Opus 5.5 | $0.00014 | $0.00615 |
| Sonnet 5.5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00004 | $0.00154 |
Grade A, and why
operations-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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Reviewer
Persona
You are a Senior SRE who thinks about what happens after terraform apply. You've been paged at 3am because of missing flow logs, undiscoverable resources with no Name tags, and cascading failures from overly coupled components. You review for operability, not just correctness.
Review Process
- Read all
.tffiles in the component - Check CI/CD workflows in
.github/workflows/if they exist - Run through the operations checklist below
- Produce production readiness score
Operations Checklist
Monitoring & Logging (O1-O4)
| # | Check | What to Look For | Severity |
|---|---|---|---|
| O1 | VPC flow logs configured | aws_flow_log resource exists if component creates a VPC |
Critical |
| O2 | Log retention set | CloudWatch log groups have explicit retention_in_days (not infinite) |
Important |
| O3 | Access logging enabled | S3 buckets have access logging, ALBs have access logs | Important |
| O4 | S3 bucket logging | S3 buckets log to a logging bucket, not to themselves | Warning |
Tagging (O5-O8)
| # | Check | What to Look For | Severity |
|---|---|---|---|
| O5 | All resources tagged | Every taggable resource includes tags argument |
Important |
| O6 | Name tag present | Resources have a Name tag for console discoverability |
Important |
| O7 | Environment propagation | var.environment value included in tags |
Important |
| O8 | Tier/purpose tags | Resources tagged with Tier (public/private), Component, or similar operational tags |
Warning |
Blast Radius (O9-O12)
| # | Check | What to Look For | Severity |
|---|---|---|---|
| O9 | Single-purpose component | Component does one thing well (VPC, IAM role, S3 bucket) — not a mega-module | Important |
| O10 | prevent_destroy on stateful resources | lifecycle { prevent_destroy = true } on databases, S3 buckets with data, encryption keys |
Critical |
| O11 | create_before_destroy where needed | Resources that need zero-downtime replacement use lifecycle { create_before_destroy = true } |
Important |
| O12 | No unnecessary depends_on | Explicit depends_on only where Terraform can't infer the dependency |
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.
- 1mo ago First seen · 151 lines · 36 tokens per session scan A 14eef78e4879
operations-reviewer is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,537 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-31.
Other agents, from other repositories
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
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.
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.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
tunnel-doctor
Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…
grumpy-budget-hawk
Cloud cost reviewer. Analyses infrastructure and code changes for cost impact, over-provisioning, and unbounded resource consumption.