Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add msaad00/agent-bom --skill scan-infragit clone --depth 1 https://github.com/msaad00/agent-bomWrote 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/skills/msaad00/agent-bom/scan-infra)<a href="https://agentmods.dev/skills/msaad00/agent-bom/scan-infra"><img src="https://agentmods.dev/badge/skills/msaad00/agent-bom/scan-infra.svg" alt="Measured on agentmods" 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.00055 | $0.01533 |
| Opus 5 | $0.00028 | $0.00766 |
| Sonnet 5 | $0.00011 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
agent-bom-scan-infra 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 3d 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.
This is a copy
95% identical to agent-bom-scan-infra — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-bom-scan-infra — Infrastructure & Cloud Security Scanner
Scans infrastructure-as-code (Terraform, CloudFormation, Kubernetes), finds secrets in config files, and runs cloud CIS benchmarks against AWS, Azure, GCP, and Snowflake.
Install
pipx install agent-bom
agent-bom iac infra/ # scan Terraform/CloudFormation/K8s
agent-bom cloud aws # AWS CIS benchmark
agent-bom cloud azure # Azure CIS benchmark
agent-bom cloud gcp # GCP CIS benchmark
agent-bom scan --snowflake --snowflake-cis-benchmark
agent-bom secrets . # find secrets in current directory
When to Use
- "check terraform" / "scan terraform"
- "scan kubernetes" / "K8s security"
- "IaC" / "infrastructure as code"
- "find secrets" / "secret scanning"
- "scan dockerfile"
- "cloud security" / "CIS benchmark"
- "misconfigurations"
Commands
# Scan IaC directory
agent-bom iac infra/
# Run cloud CIS benchmark
agent-bom cloud aws
agent-bom cloud azure
agent-bom cloud gcp
agent-bom scan --snowflake --snowflake-cis-benchmark
# Find secrets in files
agent-bom secrets .
Tools
| Tool | Description |
|---|---|
iac |
Scan Terraform, CloudFormation, Kubernetes YAML for misconfigurations |
cloud |
CIS benchmark checks (AWS, Azure v3.0, GCP v3.0, Snowflake) |
secrets |
Find secrets and credentials in files and directories |
Examples
# Scan IaC directory for misconfigurations
iac(path="infra/")
# Run AWS CIS benchmark
cloud(provider="aws")
# Find secrets in project
secrets(path=".")
Guardrails
- Confirm with the user before running cloud CIS benchmarks — these make live read-only API calls to AWS/Azure/GCP using the user's locally configured credentials.
- IaC and secrets scanning is purely local — no network calls.
- Do not modify any infrastructure files.
- Ask the user before scanning paths outside their home or project directory.
- Cloud credentials are used only to call the cloud provider's own APIs and are never transmitted elsewhere.
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.
- 3d ago Changed fc1a2c148e22
- 7d ago First seen · 175 lines · 55 tokens per session scan A 5b5ca9537574
agent-bom-scan-infra is a skill published in the GitHub repository msaad00/agent-bom (31 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 1,533 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to agent-bom-scan-infra, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
cloud-iam-deep
Cloud IAM red-team attack chain across AWS, Azure, GCP — focused on EXTERNAL exploitation paths and post-credential-discovery privilege analysis. Covers IAM enumeration (aws iam, az role, gcloud iam), STS/AssumeRole chaining, Azure Managed Identity abuse (via SSRF/leak), GCP service account JSON abuse, IMDSv1/v2…
implementing-aqua-security-for-container-scanning
Deploy Aqua Security's Trivy scanner to detect vulnerabilities, misconfigurations, secrets, and license issues in container images across CI/CD pipelines and registries.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
cis-aws-foundations-6.5
Ensure the default security group of every VPC restricts all traffic.
cis-aws-foundations-2.1.3
Ensure Organizations management account is not used for workloads.
cis-aws-foundations-2.2
Maintain current AWS account contact details.