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 commands/bomly-dev/bomly-cli/scangit clone --depth 1 https://github.com/bomly-dev/bomly-cliWhat 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.00000 | $0.01018 |
| Opus 5 | $0.00000 | $0.00509 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
scan 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bomly scan
Resolve a target's dependencies into one consolidated graph, then optionally enrich, analyze, audit, and render it. scan is the pipeline every other graph command builds on — flags you learn here work the same way on explain and diff.
Minimal invocation
bomly scan
Scans the current directory. On a small npm project:
✓ 68 packages in 1 manifest (1 direct, 67 transitive · runtime 68, dev 0)
Top-level dependencies
NAME VERSION LICENSE SCOPE VULNS
express 4.19.2 MIT runtime -
No matcher service is contacted here — enrichment columns stay empty until you ask for them. (Resolution itself can still invoke your build tool when a lockfile parser can't resolve the project; Network and Privacy has the full model.)
Choose a target
One target per invocation:
bomly scan --path ./services/api # a specific directory
bomly scan --recursive # discover nested subprojects (see --max-depth, --exclude)
bomly scan --url https://github.com/owner/repo --ref v1.2.3 # a remote Git ref
bomly scan --image ghcr.io/example/app:latest # a container image
bomly scan --sbom --path ./sbom.cdx.json # an existing SBOM
Scan Targets covers each target's semantics and limits.
Enrich, analyze, audit
The pipeline gates are independent opt-ins that compose:
# Fetch vulnerability, license, lifecycle, and scorecard data
bomly scan --enrich
# Evaluate policy against enriched data; exit 2 when a finding matches
bomly scan --enrich --audit --fail-on high
# Add reachability analysis and gate only on reachable findings
bomly scan --enrich --audit --analyze --fail-on low --fail-on reachable
--enrichis the only flag that turns on matcher network calls (Network and Privacy).--auditevaluates data already present; repeatable--fail-onconstraints AND together (any|low|medium|high|critical,reachable,exploitable). Policy flags such as--deny-license,--deny-package,--allow-vulnerability-id, and--baselineare documented in Auditors and Finding Baselines.--analyzeis experimental — read Reachability before gating on it.--warn-onlykeeps findings visible but downgrades them so the exit code stays0.
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.
- yesterday First seen · 88 lines · 0 tokens per session scan A 3e1f45545f0b
scan is a command published in the GitHub repository bomly-dev/bomly-cli (11 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,018 tokens. 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-31.
Other commands, from other repositories
audit
Scan a Rust project and produce a supply chain security gap analysis.
generate
Generate a single supply chain security config file.
verify
Verify that generated supply chain configs are valid and functional.
check-updates
Check for outdated GitHub Action SHAs and CLI tool versions in deployed workflows.
harden
Interactive wizard to generate missing supply chain security configs.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.