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 monitorgit 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/monitor)<a href="https://agentmods.dev/skills/msaad00/agent-bom/monitor"><img src="https://agentmods.dev/badge/skills/msaad00/agent-bom/monitor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/msaad00/agent-bom/monitor"><img src="https://agentmods.dev/badge/skills/msaad00/agent-bom/monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00986 |
| Opus 5.5 | $0.00019 | $0.00394 |
| Sonnet 5.5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
agent-bom-monitor 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 8d 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-monitor — Agent Fleet Monitor
Monitor agent fleet health, track trust scores, and manage agent lifecycle states across your AI infrastructure. Start a local dashboard server for continuous monitoring.
Install
pipx install agent-bom
agent-bom fleet sync # sync fleet state with latest scan
agent-bom fleet list # list all agents and trust scores
agent-bom serve # start local monitoring dashboard
When to Use
- "fleet" / "agent fleet"
- "watch agents" / "monitor agents"
- "runtime status"
- "trust scores"
- "fleet sync"
- "agent lifecycle"
- "serve dashboard" / "start dashboard"
Commands
# Sync fleet state with latest scan
agent-bom fleet sync
# List all agents with trust scores
agent-bom fleet list
# Start local monitoring dashboard
agent-bom serve
Examples
# Sync fleet
fleet_sync()
# List agents and trust scores
fleet_list()
# Start dashboard server
serve()
Example fleet list output:
Agent Fleet — 7 agents tracked
filesystem trust: 92 status: healthy last-scan: 2m ago
brave-search trust: 88 status: healthy last-scan: 2m ago
github trust: 95 status: healthy last-scan: 2m ago
slack trust: 71 status: warning last-scan: 2m ago [2 CVEs]
postgres trust: 84 status: healthy last-scan: 2m ago
linear trust: 90 status: healthy last-scan: 2m ago
notion trust: 67 status: at-risk last-scan: 2m ago [CRITICAL]
Guardrails
- Fleet monitoring is read-only — no agents are modified.
- The dashboard server runs on localhost only — no external exposure.
- Confirm with the user before starting
agent-bom serve— it binds a local port. - Trust scores are derived from local scan data; they do not contact external services.
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.
- 8d ago Changed 53f76c364dff
- 9d ago Changed b0a037436950
- 10d ago Changed 526350c6ead3
- 11d ago Changed bbff62344db6
- 14d ago Changed 44bd809dbe07
- 16d ago Changed 414c075deb68
- 17d ago Changed dec8aa79958d
- 21d ago Changed 19707b87c8ea
- 24d ago Changed e20a1d94897e
- 1mo ago First seen · 122 lines · 48 tokens per session scan A c6f6dc45e52e
agent-bom-monitor is a skill published in the GitHub repository msaad00/agent-bom (31 stars, last pushed 8d ago), licensed Apache-2.0. It adds 48 tokens to every session and 986 once invoked, about $0.0002 per session on Opus 5.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
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.
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.
scanning-container-images-with-grype
Scan container images for known vulnerabilities using Anchore Grype with SBOM-based matching and configurable severity thresholds.
red-teaming-llms-with-garak
Run NVIDIA garak probe suites against an LLM endpoint to test for jailbreaks, prompt injection, data leakage, and toxic generation, then interpret the hit-rate report for triage and reporting.
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…