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/analyze-plangit 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.00015 | $0.00367 |
| Opus 5 | $0.00008 | $0.00183 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
analyze-plan 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 3d 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.
What it actually says
Plan Analysis
Analyze a Terraform execution plan to surface security-sensitive changes, cost impacts, destructive actions, and drift before terraform apply.
Step 1: Detect Component
- Check if
src/versions.tfexists → single-component repo, component atsrc/ - 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: Locate or Generate Plan
Check for plan sources in this order:
- User provided a file path → Read it directly as plan JSON
plan.tfplanexists in component dir → Convert:terraform show -json plan.tfplan.terraform/exists in component dir → Ask user before generating:"No plan file found. I can run
terraform plan -json -lock=falseto generate one. This is read-only and won't modify state. Proceed?"- None of the above → Tell user:
"No plan available. Either run
terraform init && terraform plan -out=plan.tfplanfirst, or provide a plan JSON file path."
Step 3: Run Plan Analysis
Invoke the infra-review:terraform-plan-analyzer skill against the plan JSON.
IMPORTANT: Never run terraform apply. This is analysis only.
Step 4: Write Report
Write findings to claude/infra-review/plan-analysis.md in the repository root.
Present the change summary, any destructive warnings, security concerns, and the verdict to the user.
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.
- 3d ago First seen · 38 lines · 15 tokens per session scan A d482ea0c7e83
analyze-plan is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 367 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
account
This API allows you to manage your Scaleway Projects.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deploy
Build, test, deploy with staged rollout.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
deploy
Build a container image, push it, and deploy the service to the Akka platform. This is the transition from local development to development on the AAO platform.