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 troubleshootgit 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/troubleshoot)<a href="https://agentmods.dev/skills/msaad00/agent-bom/troubleshoot"><img src="https://agentmods.dev/badge/skills/msaad00/agent-bom/troubleshoot/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/troubleshoot"><img src="https://agentmods.dev/badge/skills/msaad00/agent-bom/troubleshoot.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00905 |
| Opus 5.5 | $0.00021 | $0.00362 |
| Sonnet 5.5 | $0.00011 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
agent-bom-troubleshoot 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 29d 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
88% identical to agent-bom-troubleshoot — 11 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.
What it actually says
agent-bom-troubleshoot — Diagnostics & Configuration Validator
Diagnoses issues, checks prerequisites, validates configurations, and reports on the health of the agent-bom installation and connected database.
Install
pipx install agent-bom
agent-bom doctor # check prerequisites and installation health
agent-bom mcp validate inventory.json # validate inventory files
agent-bom db status # check database connection status
When to Use
- "doctor" / "run doctor"
- "debug" / "help me debug"
- "why failing" / "something's broken"
- "validate config" / "check configuration"
- "check prerequisites"
- "db status" / "database status"
- "fix my setup"
Commands
# Run full diagnostic check
agent-bom doctor
# Validate configuration
agent-bom mcp validate inventory.json
# Check database status
agent-bom db status
Examples
# Run diagnostics
doctor()
# Validate config
validate()
# Check DB
db_status()
Example doctor output:
agent-bom doctor
Python 3.12.2 OK
agent-bom 0.75.9 OK
pip 24.0 OK
semgrep not found (optional — SAST scanning unavailable)
kubectl not found (optional — K8s context unavailable)
Config files found:
Claude Desktop ~/.config/Claude/claude_desktop_config.json OK
Cursor ~/.cursor/mcp.json OK
Database: SQLite ~/.agent-bom/db.sqlite OK
Last scan: 2 hours ago
Status: Ready
Guardrails
- Diagnostics are read-only — no configuration files are modified.
- Doctor checks do not transmit any data externally.
- If the user is experiencing an error, show the full diagnostic output before suggesting fixes.
- Validate configuration files before recommending changes.
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.
- 29d ago Changed e81d68f7a318
- 1mo ago Changed 296a0cdc3dc6
- 1mo ago Changed 2578bff57f5e
- 1mo ago Changed 431231847b28
- 1mo ago Changed 061538171bf3
- 1mo ago Changed 3ce753bb3ff0
- 1mo ago Changed 2148a2e7db01
- 1mo ago Changed 851d8e3ac9f0
- 1mo ago Changed b5943ee33be6
- 1mo ago First seen · 128 lines · 53 tokens per session scan A 3dbba31173ac
agent-bom-troubleshoot is a skill published in the GitHub repository msaad00/agent-bom (31 stars, last pushed 29d ago), licensed Apache-2.0. It adds 53 tokens to every session and 905 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to agent-bom-troubleshoot, differing in 11 lines, and is treated as a copy.
agent-bom-troubleshoot compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| agent-bom-troubleshootmsaad00/agent-bom | Skill | 31 | 29d ago | Apache-2.0 | A | 53 | Claude Code, Codex |
| argusAwarexone/Agentic-Bug-Hunter | Skill | 5.7k | 11d ago | MIT | A | 166 | Claude Code |
| implementing-aqua-security-for-container-scanningxalgorix/xalgorix | Skill | 1.3k | yesterday | Apache-2.0 | A | 41 | Claude Code, Codex |
| vuln-assess-phases0ld13rr/pentestcode | Skill | 930 | 2d ago | MIT | A | 41 | Claude Code, Codex |
| performing-container-security-scanning-with-trivyxalgorix/xalgorix | Skill | 1.3k | yesterday | Apache-2.0 | A | 48 | Claude Code, Codex |
| sast-ssrfutkusen/sast-skills | Skill | 1.4k | 15d ago | MIT | B | 99 | Claude Code, Codex |
| log-summarizerzhuyansen/agent-skills-hub | Skill | 493 | yesterday | MIT | A | 25 | Claude Code, Codex |