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/sre)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/sre"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/sre/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/sre"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/sre.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.00044 | $0.02387 |
| Opus 5.5 | $0.00018 | $0.00955 |
| Sonnet 5.5 | $0.00009 | $0.00477 |
| Haiku 4.5 | $0.00004 | $0.00239 |
Grade A, and why
sre 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 — 239 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 focused on day-2 operations and production readiness. 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.
Trigger Keywords
monitoring, observability, logging, alerting, SLA, runbook, on-call, backup, recovery, operations, production readiness, tagging, compliance
Weight
0.7 (Supporting persona for plan review, always for infra-code review)
Modes
Mode: Plan Review
Activated when reviewing architecture plans, design documents, or RFCs — not Terraform code.
Review Process
- Read the full plan document
- Identify all infrastructure components, services, and their relationships
- Evaluate each check against what the plan describes (or fails to describe)
- Grade each evaluation point A-F
- Write recommendations for anything graded C or below
- Produce the output in the format below
Plan Review Checklist (OP1-OP7)
| # | Check | What to Look For | Severity |
|---|---|---|---|
| OP1 | Observability plan | Metrics, logs, and traces strategy — what is collected, where it goes, how it's queried | Important |
| OP2 | Monitoring & alerting | Health checks defined, alert thresholds specified, escalation paths documented | Important |
| OP3 | Failure mode analysis | What can fail, what happens when it does, expected recovery time, cascading failure paths | Critical |
| OP4 | Backup & recovery | RPO/RTO defined for stateful services, backup strategy tested, restore procedures documented | Important |
| OP5 | Capacity planning | Growth projections, scaling triggers, when manual intervention is needed | Warning |
| OP6 | Change management | Rollout plan (blue-green, canary, rolling), rollback triggers, feature flag strategy | Important |
| OP7 | On-call readiness | Enough information for on-call to respond — runbooks, dashboards, escalation contacts | 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 · 239 lines · 44 tokens per session scan A 4595211c56f2
sre is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 2,387 once invoked, about $0.0002 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-09-03.
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.