Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Terraform and Kubernetes Infrastructure Diagram Generator

    1

    Draw your real cloud topology from Terraform, Helm, Kustomize or CDK as Mermaid, every node traced to file:line, with public exposure findings and a MAPPED, PARTIAL or EXPOSED verdict.

    $7

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Terraform and Kubernetes Infrastructure Diagram Generator

    Terraform and Kubernetes Infrastructure Diagram Generator

    Example session with this skill installed

    Diagram our payments-infra repo (Terraform in envs/dev and envs/prod, Helm charts under charts/). Only the ALB on 443 is supposed to be public. Show me what is actually exposed and how dev differs from prod.

    • Read your context and instructions
    • Compiled the terraform and kubernetes

    Infrastructure diagrams - payments-infra @ 7b3e91d (dev, prod)

    Verdict: EXPOSED Sources: Terraform, Helm Plan JSON: no
    Defaults used: intended public = ALB on 443 only Render test: passed 4/4 (mmdc)

    Exposure findings

    #SeverityResourceEnvWhy publicEvidenceFix
    1CRITICALmodule.data.aws_security_group_rule.db_ingressdev5432 open to 0.0.0.0/0envs/dev/terraform.tfvars:14 -> modules/data/sg.tf:22set db_allowed_cidrs to the app subnet CIDRs
    2HIGHService grafana (monitoring)prodtype: LoadBalancer, no loadBalancerSourceRangescharts/monitoring/values-prod.yaml:31, rendered/monitoring/templates/service.yaml:9use ClusterIP + existing ingress, or add source ranges
    3INFOmodule.edge.aws_lb.publicallinternet-facing ALB, 443modules/edge/main.tf:12intended

    Network view (prod)

    flowchart TB
      internet{{Internet}}
      subgraph vpc["vpc main (prod)"]
        subgraph pub["public subnets x2"]
          alb[public<br/>aws_lb ALB]
          glb[grafana<br/>Service LoadBalancer]
        end
        subgraph priv["private subnets x2"]
          eks[eks main<br/>node group x3]
          db[(payments<br/>aws_db_instance)]
        end
      end
      internet ==>|443| alb
      internet ==>|3000| glb
      alb -->|8080| eks
      eks -->|5432| db
      classDef exposed stroke:#d00,stroke-width:3px
      class glb exposed
    

    Environment differences

    ResourcedevprodEvidence
    node group size13envs/*/terraform.tfvars:6
    RDS multi_azfalsetrueenvs/*/terraform.tfvars:11
    db_allowed_cidrs0.0.0.0/0app subnetsenvs/*/terraform.tfvars:14

    Unconfirmed (not drawn)

    • module.waf - registry source, not in .terraform/modules - run terraform init -backend=false (needs your yes)
    • aws_route53_record.alias - for_each over var.extra_domains, no value in any tfvars

    Next steps

    • Wrote docs/infrastructure/01-04, exposure.md, evidence.md; last verified 7b3e91d
    • Fix findings 1 and 2, then rerun the exposure check
    exposure.md, evidence.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Infrastructure diagrams are usually hand-drawn once and wrong by the next sprint. An AI asked to draw your cloud from scratch will happily add subnets, NAT gateways or regions that your code never declares. This skill reads the infrastructure-as-code itself and requires a file and line for every boundary, resource and connection.

    What it does:

    • Inventories Terraform/OpenTofu roots, modules and tfvars, Kubernetes manifests, Helm charts, Kustomize overlays, CloudFormation/CDK output, Pulumi programs and docker-compose files
    • Renders locally where possible (helm template, kubectl kustomize, cdk synth with lookups off) and uses terraform show -json plan output if you provide it
    • Resolves resources through module sources, count and for_each, and lists anything it cannot resolve as Unconfirmed instead of drawing it
    • Draws four Mermaid views: network topology (account, region, VPC, public and private subnets), Kubernetes, data stores and secrets, and per-environment differences. D2 or architecture-beta on request
    • Flags internet-facing resources (IGW routes, 0.0.0.0/0 rules, public buckets and databases, LoadBalancer services, public cluster endpoints) as findings with severity
    • Applies size rules, a legend on every diagram, a docs/infrastructure/ file layout and a drift check against a later commit or plan JSON
    • Ends with a verdict of MAPPED, PARTIAL or EXPOSED

    Who it's for: platform and DevOps engineers, SREs, security reviewers and tech leads who need an accurate infrastructure picture for onboarding, audits or design reviews.

    Honesty note: the skill is read-only and never needs cloud credentials. It does not run apply, plan or destroy, and it runs terraform init only if you say yes. It shows what the code declares, not what is live in your account, so resources created in the console are not shown.

    Diagrams show what the infrastructure code (and any plan JSON you supply) declares at one commit, not what is live in the cloud account. Console-created resources, live drift and the contents of remote modules that have not been downloaded are not visible. Values that depend on data sources, remote state or cluster lookups are listed as Unconfirmed. Mermaid architecture-beta icon packs do not work on GitHub or GitLab.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    Requires

    @mermaid-js/mermaid-cli
    Node.js
    Git

    Permissions

    Terminal / Shell
    Read Files
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    SKILL.md (the workflow, resolution rules, exposure severities, verdict rules and output template) and references/iac-sources-and-diagram-syntax.md (read-only render commands, terraform show -json fields, exposure checks per cloud, Mermaid flowchart, architecture-beta and D2 skeletons, size rules and sources). That is the whole package.

    Any agent that loads SKILL.md skills, such as Claude Code, Codex CLI, Cursor, VS Code Copilot and Gemini CLI. It needs read access to the repo. Shell access lets it render Helm, Kustomize and CDK locally and render-test the Mermaid output, which improves results.

    No. It never runs apply, destroy, plan, deploy or pulumi up, and it never asks for credentials. terraform init downloads providers and modules, so the skill asks before running it. If you already have plan JSON from terraform show -json, it can use that.

    It sees only what the code and any plan JSON you provide declare. Resources created in the console, live drift, and the contents of remote modules that have not been downloaded are not shown, and are listed as Unconfirmed where they are referenced. Custom cloud icons do not render on GitHub or GitLab, so the default diagrams use plain shapes.

    A plain prompt tends to produce a plausible cloud picture. This skill makes the agent resolve modules and variables, prove each element with a file and line, decide public versus private from route and rule evidence rather than names, list exposure findings by severity, and keep each diagram small enough to read.

    New in DevOps & Cloud