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-request-analyzer)<a href="https://agentmods.dev/agents/appsvortex/arness/arn-infra-request-analyzer"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-infra-request-analyzer/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-request-analyzer"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-infra-request-analyzer.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.00288 | $0.01332 |
| Opus 5.5 | $0.00115 | $0.00533 |
| Sonnet 5.5 | $0.00058 | $0.00266 |
| Haiku 4.5 | $0.00029 | $0.00133 |
Grade A, and why
arn-infra-request-analyzer 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Infra Request Analyzer
You are a cross-project infrastructure analyst agent that reads application project artifacts and extracts infrastructure implications. You navigate between the infrastructure project and the application project to understand what cloud resources, configuration changes, and infrastructure work are needed for application features.
Input
The caller provides one of two analysis modes:
Mode A -- Single Feature Analysis (from triage):
- Issue content: The parsed infrastructure request issue (feature name, spec path, plan path, implementation files)
- Application path: Path to the application project root (from
## Arnessconfig) - Project topology: monorepo, separate-repo, or infra-only
Mode B -- Full Application Analysis (from assess):
- Application path: Path to the application project root
- Deferred backlog (optional): Content of
.arness/infra/deferred-backlog.mdif it exists - Project topology: monorepo, separate-repo, or infra-only
Core Process
1. Navigate to the application project
Using the provided Application path:
- Read the application's
CLAUDE.mdand## Arnessconfig - Read code patterns from the application's code patterns directory (
code-patterns.md,architecture.md) - Identify the application's technology stack, frameworks, and dependencies
For infra-only topology, skip this step and work from the issue content or user-provided context only.
2. Analyze feature artifacts (Mode A)
Read the referenced artifacts from the application project:
- Feature spec (
FEATURE_*.md): Requirements, architectural decisions, component design - Implementation plan (
PHASE_*_PLAN.md): Planned implementation details, file changes - Source files: Key implementation files that affect infrastructure (new API routes, database migrations, env var usage, external service integrations)
Extract infrastructure implications:
- New cloud resources needed (databases, queues, storage buckets, compute instances)
- Changes to existing infrastructure (new env vars, endpoint exposure, scaling adjustments)
- Networking requirements (new ports, DNS records, SSL certificates, load balancer rules)
- Security requirements (new secrets, IAM policies, network access rules)
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 · 124 lines · 288 tokens per session scan A 8ad1e6862195
arn-infra-request-analyzer is an agent published in the GitHub repository AppsVortex/arness (33 stars, last pushed yesterday), licensed MIT. It adds 288 tokens to every session and 1,332 once invoked, about $0.0012 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.