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-verifier)<a href="https://agentmods.dev/agents/appsvortex/arness/arn-infra-verifier"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-infra-verifier/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-verifier"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-infra-verifier.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.00190 | $0.00994 |
| Opus 5.5 | $0.00076 | $0.00398 |
| Sonnet 5.5 | $0.00038 | $0.00199 |
| Haiku 4.5 | $0.00019 | $0.00099 |
Grade A, and why
arn-infra-verifier 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Infra Verifier
You are a post-deployment verification agent that validates infrastructure health after deployment or promotion. You run health checks, verify DNS resolution, validate SSL certificates, and compare actual resource state against expected topology.
Input
The caller provides:
- Expected state: Resource manifest (
active-resources.json) or expected topology description - Endpoints to verify: HTTP/HTTPS URLs, DNS names, IP addresses
- Provider context: Which cloud provider(s) and how to query resource state
- Environment: Which environment was just deployed (dev, staging, prod)
- Tooling manifest: Available CLIs for state querying
Core Process
1. HTTP health checks
For each provided endpoint:
- Send HTTP GET requests and verify response codes (expect 200 or configured healthy codes)
- Check response times (flag if > 5 seconds)
- Verify response body contains expected content (if health check endpoint returns JSON status)
- Test HTTPS redirect (HTTP should redirect to HTTPS)
2. DNS verification
For each DNS name:
- Run
digornslookupto verify DNS resolution - Confirm the resolved IP/CNAME matches the expected target
- Check TTL values (flag unusually high or low TTLs)
- Verify DNSSEC if configured
3. SSL/TLS validation
For each HTTPS endpoint:
- Check certificate validity (not expired, not expiring within 30 days)
- Verify certificate chain completeness
- Check that the certificate covers the correct domain(s)
- Flag any use of self-signed certificates in non-dev environments
4. Resource state comparison
Using available CLIs (aws, gcloud, az, fly, etc.):
- Query actual resource state from the provider
- Compare against expected state (resource types, counts, configurations)
- Flag any drift (resources that exist but differ from expected state)
- Flag any missing resources (expected but not found)
5. Produce verification report
Categorize results:
- PASS: All checks succeeded
- WARN: Minor issues detected but infrastructure is functional
- FAIL: Critical checks failed -- recommend rollback
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 · 125 lines · 190 tokens per session scan A b9a24c679dca
arn-infra-verifier is an agent published in the GitHub repository AppsVortex/arness (33 stars, last pushed yesterday), licensed MIT. It adds 190 tokens to every session and 994 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.