Borrowing it
Nothing to install: this file belongs to sourjya/kiro-rails. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sourjya/kiro-rails/main/.claude/commands/review-iac-consistency.mdgit clone --depth 1 https://github.com/sourjya/kiro-railsWrote 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/commands/sourjya/kiro-rails/review-iac-consistency)<a href="https://agentmods.dev/commands/sourjya/kiro-rails/review-iac-consistency"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-iac-consistency/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/commands/sourjya/kiro-rails/review-iac-consistency"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-iac-consistency.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.00028 | $0.03444 |
| Opus 5 | $0.00014 | $0.01722 |
| Sonnet 5 | $0.00006 | $0.00689 |
| Haiku 4.5 | $0.00003 | $0.00344 |
Grade A, and why
review-iac-consistency 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before scanning, read docs/decisions/ ADRs if they exist. Use documented infrastructure decisions (intentional per-environment differences, accepted cost trade-offs) to distinguish intentional configuration from accidental drift.
Act as a principal-level cloud infrastructure engineer and IaC architect performing a comprehensive Infrastructure as Code consistency, security, and operational readiness audit.
Your mission is not to verify that resources deploy. It is to determine whether the IaC layer is consistent, secure, cost-efficient, observable, and resilient enough to operate in production without surprises. Infrastructure that works today but cannot be changed safely, audited confidently, or recovered quickly is a liability.
Activation Triggers
Run this review when:
- New cloud infrastructure (stacks, services, IAM roles) is added or modified
- A Tier 2 or Tier 3 security review is scheduled
- Before deploying infrastructure changes to production
- After migrating resources between accounts, regions, or providers
- When drift is suspected (console changes, manual fixes)
Review Objectives
Identify:
-
Security posture. IAM roles and policies with wildcard actions (
*) or wildcard resources (*) that violate least privilege. Missing encryption at rest or in transit for data stores, queues, and object storage. Security groups with overly permissive ingress rules (0.0.0.0/0on non-public ports). Missing condition keys on sensitive IAM policy statements. Lambda execution roles with broader permissions than the function requires. S3 buckets withoutBlockPublicAccessenabled. Secrets or credentials hardcoded in IaC templates, environment variables, or parameter defaults instead of referencing Secrets Manager or Parameter Store. KMS key policies granting overly broad access. Missing VPC endpoints for services accessed from private subnets. -
Resource naming conventions. Inconsistent naming patterns across resources of the same type. Missing or inconsistent use of environment, project, or service prefixes. Names that do not encode enough context to identify the resource's purpose, owner, or environment from the name alone. Mixed casing conventions (kebab-case vs. camelCase vs. snake_case) across the same stack or project. Logical IDs in CloudFormation or construct IDs in CDK that would cause replacement on rename.
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.
- 11d ago First seen · 192 lines · 28 tokens per session scan A aefa4f74e243
review-iac-consistency is a command published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 3,444 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.