agentmods.dev

arn-infra-review-change

arn-infra-review-change is a skill for Claude Code from AppsVortex/arness. It costs 105 tokens per session (2,236 once invoked), scanned A, original, MIT.

A post-change review tool for infrastructure work. It reads the plans and execution reports, then produces a structured result showing whether the completed change passes, needs warnings, or needs fixes.

In plain words
What is it for?
It reviews completed infrastructure changes against seven quality areas and returns a PASS, WARN, or NEEDS_FIXES verdict, with suggested remediation when needed.
Why use it?
It provides a quality checkpoint after infrastructure changes run, so problems can be identified before the work is documented as complete. For failures, it points to corrective actions and affected phases.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the arn-infra plugin — 25 skills, 10 agents shipped together

not rated 33repo yesterday A scan 105 tokens original MIT

Good fit It reviews completed infrastructure changes against seven quality areas and returns a PASS, WARN, or NEEDS_FIXES verdict, with suggested remediation when needed.

Compare 6 skills from other repositories ↓
View source ↗ AppsVortex/arness arness.appsvortex.com
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add AppsVortex/arness
Claude Code
/plugin install arn-infra

Made for: Claude Code.

Or install arn-infra, the plugin that ships this one along with the rest of its 25 skills, 10 agents.

Wrote 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.

agentmods badge for arn-infra-review-change

README.md
[![agentmods](https://agentmods.dev/badge/skills/appsvortex/arness/arn-infra-review-change/github.svg)](https://agentmods.dev/skills/appsvortex/arness/arn-infra-review-change)
Your own site
<a href="https://agentmods.dev/skills/appsvortex/arness/arn-infra-review-change"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-infra-review-change/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.

agentmods 80×15 button for arn-infra-review-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/appsvortex/arness/arn-infra-review-change"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-infra-review-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,236 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00105 $0.02236
Opus 5.5 $0.00042 $0.00894
Sonnet 5.5 $0.00021 $0.00447
Haiku 4.5 $0.00011 $0.00224

Measured yesterday against content hash e5d3000e2926, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

arn-infra-review-change 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.

plugins/arn-infra/skills/arn-infra-review-change/SKILL.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Arness Infra Review Change

Perform a comprehensive post-execution quality review of completed infrastructure changes. This skill reads all phase execution reports, the original spec, and the source plan, then invokes the arn-infra-change-reviewer agent to evaluate 7 quality categories and produce a structured review report with an overall verdict.

This is the quality gate between execution and documentation. A PASS or WARN verdict enables documentation generation. A NEEDS_FIXES verdict identifies specific remediation actions and suggests re-executing affected phases.

Prerequisites

Read ## Arness from the project's CLAUDE.md. If no ## Arness section exists or Arness Infra fields are missing, inform the user: "Arness Infra is not configured for this project yet. Run /arn-infra-wizard to get started — it will set everything up automatically." Do not proceed without it.

Check the Deferred field. If Deferred: yes, inform the user: "Infrastructure is in deferred mode. Change review is not available until infrastructure is fully configured. Run /arn-infra-assess to un-defer." Stop.

Extract:

  • Infra plans directory -- where structured plan projects live (default: .arness/infra-plans)
  • Infra specs directory -- where change specs are stored (default: .arness/infra-specs)
  • Providers -- cloud providers configured
  • Environments -- environment names in promotion order
  • Experience level -- derived from user profile. Read ~/.arness/user-profile.yaml (or .claude/arness-profile.local.md if it exists — project override takes precedence). Apply the experience derivation mapping from ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/experience-derivation.md. If no profile exists, check for legacy Experience level in ## Arness as fallback.
  • Cost threshold -- monthly budget limit for cost compliance evaluation (default: 100)

Locate the Completed Change Project

Search for completed or in-progress change projects:

Read the full file on GitHub · 229 lines

Changes

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.

  1. yesterday First seen · 229 lines · 105 tokens per session scan A e5d3000e2926

Subscribe to this mod's changes

arn-infra-review-change is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 2,236 once invoked, about $0.0004 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.

Claude CodeCode reviewDevOps and cloudai-workflowsclaude-code-plugindeveloper-toolsinfrastructure-as-codemcp
Related

Other skills, from other repositories

brooks-sweep

Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…

hyhmrright/brooks-lint · 178 tokens

critical-code-reviewer

Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.

posit-dev/skills · 67 tokens

pr-review

Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…

nitinjain999/platform-skills · 81 tokens

genshijin-review

A compact pull-request review format that writes one actionable finding per line in Japanese or English.

InterfaceX-co-jp/genshijin · 78 tokens

pr-review

Use when the user wants to deeply review a pull/merge request or a local diff — "review this PR", "grill the MR", "stress-test this diff", "deep-dive code review", "code review before merge", or when they name a PR/MR URL, number, branch, commit range (A..B/A...B), tag or SHA. Works on GitHub (gh), GitLab (glab), or a…

procoders/superpowers-v · 112 tokens

shipyard-handoff

Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress. Use when the user says "handoff", "save context", or "I'm done for now", or when a long session ends and its state should be recorded.

lgbarn/shipyard · 60 tokens