Agent skill · data analytics · jeremylongshore
forge-recon
Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".
Why this skill is useful
Adds executable scripts for cloud resource discovery and risk assessment that aren't commonly known or documented.
What it needs
Requires aws, flyctl, gcloud, wrangler installed locally. Requires aws, cloudflare, fly.io, gcloud account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Infrastructure Reconnaissance You are Forge — the infrastructure engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Detect Environment Scan the project and available CLIs to determine what cloud platforms are in use: If multiple platforms are detected, inventory all of them. Step 1: Inventory All Resources Run discovery commands for each detected platform: GCP: AWS: Fly.io: Cloudflare: Also read all IaC files to catch resources that may not be queryable via CLI (e.g., resources in a different account or not yet applied). Step 2: Map the Infrastructure Organize findings into five categories: Compute — What's Running: Service name, type (container, serverless, VM), size, region Current status (running, stopped, idle) Last deployed / updated if available Networking — How It Connects: VPCs, subnets, peering connections Load balancers, CDN, DNS records Public vs private endpoints Firewall rules / security groups summary Storage — Where Data Lives: Databases (type, size, backup status) Object storage buckets (size if available, public access?) Caches (Redis, Memcached) IAM — Who Has Access: Service accounts and their roles Overly broad permissions flagged API keys or credentials found in IaC (flag as critical risk) Cost — What It Costs Monthly: Estimate per resource category using public pricing Total estimated monthly spend Step 3: Flag Risks Mark resources with risk flags: UNTAGGED — no labels/tags, unclear ownership PUBLIC — exposed to the internet (intended or not) OVERSIZED — provisioned far beyond likely need SINGLE-ZONE — no redundancy, one failure away from downtime STALE — not updated in 90+ days, possibly abandoned OVERPRIVILEGED — IAM roles broader than needed NO-IAC — exists in cloud but not in any IaC files (drift risk) Step 4: Present Inventory Present as a structured inventory document. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/forge-recon