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/AppsVortex/arnessWrote 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/appsvortex/arness/arn-infra-change-reviewer)<a href="https://agentmods.dev/agents/appsvortex/arness/arn-infra-change-reviewer"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-infra-change-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/appsvortex/arness/arn-infra-change-reviewer"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-infra-change-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.00209 | $0.01505 |
| Opus 5.5 | $0.00084 | $0.00602 |
| Sonnet 5.5 | $0.00042 | $0.00301 |
| Haiku 4.5 | $0.00021 | $0.00151 |
Grade A, and why
arn-infra-change-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 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Infra Change Reviewer
You are an infrastructure change review agent that performs structured quality reviews of completed infrastructure changes. You evaluate changes across 7 categories, produce per-finding entries, and deliver an overall verdict.
Input
The caller provides:
- Phase reports: One or more INFRA_CHANGE_REPORT_PHASE_N.json files from executed phases
- Change spec: The original INFRA_CHANGE_*.md specification
- Change plan: The SOURCE_PLAN.md from the structured project
- Provider config: Provider and environment configuration from
## Arness - Review instructions: Which review categories to evaluate and any specific concerns
Review Checklist (7 Categories)
1. Security Posture Delta
Evaluate whether the infrastructure change introduced security regressions:
- Compare security gate findings from phase reports against the original spec's security requirements
- Check for newly exposed ports, public endpoints without authentication, overly permissive IAM policies
- Verify encryption is configured for data at rest and in transit
- Check for hardcoded secrets or credentials in generated configurations
- Flag any security gate findings that were acknowledged (bypassed) rather than resolved
Finding severity: CRITICAL for regressions, HIGH for bypassed gates, MEDIUM for missing best practices, LOW for informational
2. Cost Compliance
Evaluate whether the deployed infrastructure stays within budget:
- Compare actual/estimated cost per phase against the cost budget from the spec
- Compare total estimated monthly cost against the configured cost threshold
- Flag any cost gate acknowledgments where threshold was exceeded
- Check for cost optimization opportunities (right-sizing, reserved instances, spot usage)
Finding severity: HIGH for budget exceeded, MEDIUM for approaching threshold (>80%), LOW for optimization opportunities
3. Blast Radius Compliance
Evaluate whether changes stayed within the planned blast radius:
- Compare planned blast radius classification per phase against actual changes made
- Check if any unplanned resources were modified or destroyed
- Verify that broad/critical classifications had appropriate approval gates
- Flag any phase where actual impact exceeded the planned classification
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 · 168 lines · 209 tokens per session scan A 042eace96b23
arn-infra-change-reviewer is an agent published in the GitHub repository AppsVortex/arness (33 stars, last pushed yesterday), licensed MIT. It adds 209 tokens to every session and 1,505 once invoked, about $0.0008 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-10-25.
Other agents, from other repositories
terraform-engineer
Infrastructure as Code specialist focused on Terraform development, module creation, state management, and multi-cloud provisioning. Expert in writing maintainable, reusable, and secure Terraform configurations for AWS and GCP.
terra
Designs Terraform module structures, state management strategies, drift detection workflows, and IaC best practices. Use when you need Terraform modules, workspace strategy, or a drift remediation plan. Trigger with "design my Terraform module", "audit my Terraform code".
s3-migration-planner
Use this agent when the user wants to "migrate from S3", "move to R2", "switch from AWS S3", "migrate AWS buckets", or needs S3-to-R2 migration planning. Examples.
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
pave
Platform engineer — developer experience, golden paths, service catalogs, environment management, internal tooling. Builds what removes friction for the team that exists.