infra-plan-review SKILL.md skillA
infra-plan-review from personalclaw/personalclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add personalclaw/personalclaw/infra-plan-review@git:20260817.1f97d59Pins git:20260817.1f97d59 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- personalclaw/personalclaw
- Path
src/personalclaw/packs/bundled/infra-ops/skills/infra-plan-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260817.1f97d59, committed Aug 17, 2026
- Size
- 1,277 bytes
- Repository stars
- 10
- License
- MIT
Read a Terraform plan and report what it would create, replace and destroy — counts first, reasoning second.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Review a Terraform plan ## Steps 1. Ask for the plan output (a saved `terraform plan` text file, or the path to run it in). If neither exists yet, say so and stop — there is nothing to review. 2. Count the actions the plan reports: create, update, replace, destroy. Report the four counts before any commentary, so the shape of the change is visible before an opinion about it. 3. List every RESOURCE ADDRESS the plan would destroy or replace, one per line. A replace is a destroy plus a create, so it belongs in this list even when the resource name is unchanged. 4. For each destroy or replace, name the attribute that forces it, quoting the line from the plan. If the plan does not say, write "the plan does not say" rather than guessing. ## What not to do - Do not run `terraform apply`, and do not offer to. This skill reads a plan; applying is a separate decision a human makes with the counts in front of them. - Do not estimate cost. The plan does not contain prices, so any number here would be invented. - Do not summarise a plan you could not read in full. Say which part was truncated.
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_55r3wd5h3b2fqivj/a10efabee0b4507d13f887737cb1c158ea9360d21b3d813c5a9dc7c1d5c620a0.json
Then /plugin install infra-plan-review@markdownregistry-55r3wd5h3b2fqivj in Claude Code. It installs git:20260817.1f97d59, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add personalclaw/personalclaw/infra-plan-review@sha256:a10efabee0b4507dThe line at the top of this page pins the label git:20260817.1f97d59, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_55r3wd5h3b2fqivj)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in personalclaw/personalclaw/infra-plan-review since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of infra-plan-review from somewhere else? Ask it: where did my infra-plan-review come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Aug 17, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/infra-plan-review/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1277 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
personalclaw/personalclaw · 10 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_55r3wd5h3b2fqivj GET https://markdownregistry.com/api/v1/resolve?ref=personalclaw/personalclaw/infra-plan-review GET https://markdownregistry.com/api/v1/blob/a10efabee0b4507d13f887737cb1c158ea9360d21b3d813c5a9dc7c1d5c620a0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.