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 agentmods add skills/msaad00/agent-bom/enforcenpx skills add msaad00/agent-bom --skill enforcegit 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/enforce)<a href="https://agentmods.dev/skills/msaad00/agent-bom/enforce"><img src="https://agentmods.dev/badge/skills/msaad00/agent-bom/enforce.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 | $0.00050 | $0.00973 |
| Opus 5 | $0.00025 | $0.00487 |
| Sonnet 5 | $0.00010 | $0.00195 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
agent-bom-enforce 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.
What it actually says
agent-bom-enforce — Runtime Policy Enforcement
Enforces security policies on MCP tool calls and blocks dangerous operations at runtime. Runs a local proxy that intercepts MCP calls and evaluates them against policy-as-code rules.
Install
pipx install agent-bom
agent-bom gateway init-policy -o policy.json --format proxy --mode enforce
agent-bom proxy --url https://mcp.example.com --policy policy.json
When to Use
- "block risky calls" / "block dangerous MCP calls"
- "apply policy" / "enforce policy"
- "proxy" / "MCP proxy"
- "runtime protection"
- "policy enforcement"
- "intercept MCP calls"
Commands
# Start the enforcement proxy
agent-bom gateway init-policy -o policy.json --format proxy --mode enforce
agent-bom proxy --url https://mcp.example.com --policy policy.json
Example Policy File
# policy.yaml
rules:
- id: block-shell-exec
description: Block shell execution tool calls
match:
tool: "bash|shell|exec|run_command"
action: block
severity: critical
- id: require-path-allowlist
description: Restrict filesystem access to allowed paths
match:
tool: "read_file|write_file|list_directory"
args.path:
not_starts_with: ["/home/", "/tmp/"]
action: block
severity: high
Guardrails
- IMPORTANT: Do not start the proxy or apply policies without explicit user confirmation — enforcement changes how MCP calls are processed.
- Confirm the policy file contents with the user before applying.
- Do not enable proxy mode autonomously — always ask the user first.
- Audit logs are written locally only; no data is transmitted externally.
- This skill has
disable-model-invocation: true— do not auto-run enforcement actions.
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 First seen · 115 lines · 50 tokens per session scan A 28782830ee95
agent-bom-enforce is a skill published in the GitHub repository msaad00/agent-bom (31 stars, last pushed 3d ago), licensed Apache-2.0. It adds 50 tokens to every session and 973 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
scanning-container-images-with-grype
Scan container images for known vulnerabilities using Anchore Grype with SBOM-based matching and configurable severity thresholds.
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.
sbom-analysis
Analyzes Software Bills of Materials (SBOMs) for completeness against NTIA minimum elements, interprets VEX status documents, performs transitive dependency risk analysis, and detects license conflicts. Supports CycloneDX 1.5 and SPDX 2.3 formats with CSAF-based VEX correlation. Auto-invoked when SBOM files are…
dependency-scanning
Analyzes project dependencies for known vulnerabilities, license risks, and supply chain integrity. Auto-invoked when package manifests (package.json, requirements.txt, go.mod, pom.xml, Cargo.toml) are shared or when discussing dependency security. Produces an SBOM assessment with CVE findings triaged by EPSS and CISA…
sca-trivy
Software Composition Analysis (SCA) and container vulnerability scanning using Aqua Trivy for identifying CVE vulnerabilities in dependencies, container images, IaC misconfigurations, and license compliance risks. Use when: (1) Scanning container images and filesystems for vulnerabilities and misconfigurations, (2)…