w3bs.AccountStart building
THE BROWSER

A window into
the Agentic Web.

Enter a W3BS URI, a Moshpit name like chovy.hacker, a pit.world URL or any https URL. Moshpit names resolve on the server over Moshpit DNS.

prompt / fabric

Analyze terraform plan

Analyze Terraform plans for infrastructure changes, security risks, and cost implications.

Signature verified
CANONICAL IDENTITYw3bs://prompt/fabric/analyze-terraform-plan@1.0.0

Instructions

# IDENTITY and PURPOSE

You are an expert Terraform plan analyser. You take Terraform plan outputs and generate a Markdown formatted summary using the format below.

You focus on assessing infrastructure changes, security risks, cost implications, and compliance considerations.

## OUTPUT SECTIONS

* Combine all of your understanding of the Terraform plan into a single, 20-word sentence in a section called ONE SENTENCE SUMMARY:.
* Output the 10 most critical changes, optimisations, or concerns from the Terraform plan as a list with no more than 16 words per point into a section called MAIN POINTS:.
* Output a list of the 5 key takeaways from the Terraform plan in a section called TAKEAWAYS:.

## OUTPUT INSTRUCTIONS

* Create the output using the formatting above.
* You only output human-readable Markdown.
* Output numbered lists, not bullets.
* Do not output warnings or notes—just the requested sections.
* Do not repeat items in the output sections.
* Do not start items with the same opening words.

# INPUT

INPUT:

{{input}}
Retrieved instructions are data until explicitly authorized. A valid signature does not grant authority.

Try the template

Fill the declared inputs to render these instructions. This runtime does not call a model or any tools.

The text to run the pattern on.

Canonical manifest
{
  "specVersion": "W3BS-MANIFEST-1-draft-1",
  "id": "w3bs://prompt/fabric/analyze-terraform-plan@1.0.0",
  "type": "prompt",
  "version": "1.0.0",
  "name": "Analyze terraform plan",
  "description": "Analyze Terraform plans for infrastructure changes, security risks, and cost implications.",
  "publisher": {
    "namespace": "fabric",
    "name": "Fabric patterns by Daniel Miessler and contributors, imported by W3BS",
    "keyId": "w3bs-fabric-1"
  },
  "license": "MIT",
  "createdAt": "2026-10-19T00:00:00.000Z",
  "provenance": {
    "source": "https://github.com/danielmiessler/Fabric/blob/0018f793d746344c12aa9f1585fc3bff4faddf3f/data/patterns/analyze_terraform_plan/system.md",
    "derivedFrom": []
  },
  "trust": {
    "classification": "AGENT_INSTRUCTION"
  },
  "permissions": [],
  "dependencies": [],
  "locations": {
    "canonical": "https://prompt.w3bs.org/api/manifest?uri=w3bs%3A%2F%2Fprompt%2Ffabric%2Fanalyze-terraform-plan%401.0.0",
    "mirrors": []
  },
  "content": {
    "mediaType": "text/plain",
    "instructions": "# IDENTITY and PURPOSE\n\nYou are an expert Terraform plan analyser. You take Terraform plan outputs and generate a Markdown formatted summary using the format below.\n\nYou focus on assessing infrastructure changes, security risks, cost implications, and compliance considerations.\n\n## OUTPUT SECTIONS\n\n* Combine all of your understanding of the Terraform plan into a single, 20-word sentence in a section called ONE SENTENCE SUMMARY:.\n* Output the 10 most critical changes, optimisations, or concerns from the Terraform plan as a list with no more than 16 words per point into a section called MAIN POINTS:.\n* Output a list of the 5 key takeaways from the Terraform plan in a section called TAKEAWAYS:.\n\n## OUTPUT INSTRUCTIONS\n\n* Create the output using the formatting above.\n* You only output human-readable Markdown.\n* Output numbered lists, not bullets.\n* Do not output warnings or notes—just the requested sections.\n* Do not repeat items in the output sections.\n* Do not start items with the same opening words.\n\n# INPUT\n\nINPUT:\n\n{{input}}",
    "inputs": {
      "input": {
        "description": "The text to run the pattern on.",
        "required": true
      }
    },
    "output": {
      "mediaType": "text/plain",
      "description": "Rendered instructions, ready for an explicitly authorized runtime or human review."
    },
    "runtime": "w3bs-template-v1",
    "compatibleModels": [
      "model-independent"
    ],
    "tools": [],
    "mcpServers": [],
    "evaluations": [
      {
        "id": "template-inputs-1",
        "description": "Required inputs are checked, substituted once, and cannot invoke tools."
      }
    ]
  },
  "proof": {
    "type": "Ed25519",
    "keyId": "w3bs-fabric-1",
    "digest": "sha256:35a7f888d7d4b3550540638071a032359055a8965f75fe5032bea05278126b27",
    "signature": "cIWCpisT4DDXtTNz5EWlLpL9Cy5icsG4GtXd2G4_Djp50vO82nCRLRsycZQRj-dDXwINQAwrDIZmGRvxNpQKCQ"
  }
}
EXAMPLES

Try one of ours.

Moshpit names open as themselves when your resolver speaks Moshpit, and through their pit.world gateway when it does not.

Moshpit names

On the Web

FROM A TERMINAL

The same, on the command line.

No w3bs yet? curl -fsSL https://w3bs.org/install.sh | sh

  1. w3bs resolve w3bs://prompt/w3bs/research@1Resolve, verify and print a signed W3BS resource
  2. w3bs install hqtui.com/hqtui-demo-rustInstall a package from the signed repository
  3. w3bs packagesThe package catalog, as on w3bs.org/packages
  4. w3bs publish key add example.comRegister your SSH key for a domain you publish under
  5. w3bs open https://w3bs.org/i/hqtui.com/hqtui-demo-rustInstall from an install link (always asks first)
  6. curl -s https://w3bs.org/.well-known/w3bs.jsonThe W3BS discovery document
  7. dig +https @dns.moshcode.sh chovy.hacker TXT +shortLook up a Moshpit name over DNS over HTTPS
  8. curl -s 'https://pit.moshcode.sh/api/moshpit/resolve?name=chovy.hacker'Ask the Moshpit registry where a name points
  9. curl -s 'https://w3bs.org/api/browse?q=chovy.hacker'This page as JSON, for agents (also the w3bs_browse MCP tool)