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 commands/infraspecdev/tesseract/review-componentgit 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.00022 | $0.00623 |
| Opus 5 | $0.00011 | $0.00311 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
review-component 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 2d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Component Review
Run a comprehensive review of the current Terraform component from 4 perspectives. Follow this process exactly:
Pre-flight: Atmos Hygiene Check
Before dispatching agents, invoke the infra-review:atmos-component-hygiene skill to run a quick hygiene check. If critical issues are found (missing versions.tf, committed backend.tf), report them immediately — they should be fixed before a full review.
Step 1: Detect Component
Identify the component to review:
- Check if
src/versions.tfexists → single-component repo, reviewsrc/ - Check if
components/terraform/exists → multi-component repo, ask user which component - Neither → report "This doesn't appear to be a Terraform component repository"
Step 2: Dispatch Reviewers
Run all 4 reviewer agents sequentially against the component. For each agent, use the Agent tool with the appropriate agent type:
-
Security Review — Dispatch the
infra-review:security-revieweragent- Provide all
.tffiles from the component directory - Collect findings
- Provide all
-
Architecture Review — Dispatch the
infra-review:architecture-revieweragent- Provide all
.tffiles from the component directory - Collect findings
- Provide all
-
Operations Review — Dispatch the
infra-review:operations-revieweragent- Provide all
.tffiles and CI workflows from.github/workflows/ - Collect findings
- Provide all
-
Cost Review — Dispatch the
infra-review:cost-revieweragent- Provide all
.tffiles from the component directory - Collect findings
- Provide all
Step 3: Consolidated Report
After all 4 agents complete, write a consolidated report to claude/infra-review/review.md in the repository root:
# Terraform Component Review
**Component:** [name]
**Date:** [date]
**Reviewers:** Security, Architecture, Operations, Cost
## Summary
| Dimension | Grade/Score | Key Finding |
|-----------|------------|-------------|
| Security | [posture] | [top finding] |
| Architecture | [grade] | [top finding] |
| Operations | [score]/10 | [top finding] |
| Cost | [efficiency] | [top finding] |
## Critical Issues (Action Required)
[List any Critical/Must-Fix issues from all 4 reviews]
## Detailed Findings
### Security
[Full security review output]
### Architecture
[Full architecture review output]
### Operations
[Full operations review output]
### Cost
[Full cost review output]
## Recommended Priority Order
1. [Most important fix across all dimensions]
2. [Second]
3. [Third]
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.
- 2d ago First seen · 87 lines · 22 tokens per session scan A b99823932321
review-component is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 623 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.