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/sbom-tool/gh-guard/verifygit clone --depth 1 https://github.com/sbom-tool/gh-guardWrote 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/commands/sbom-tool/gh-guard/verify)<a href="https://agentmods.dev/commands/sbom-tool/gh-guard/verify"><img src="https://agentmods.dev/badge/commands/sbom-tool/gh-guard/verify.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.00012 | $0.00880 |
| Opus 5 | $0.00006 | $0.00440 |
| Sonnet 5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
verify 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify — Post-Generation Validation
Verify that generated supply chain security configs are syntactically valid, internally consistent, and ready to deploy.
Workflow
Step 1: Find Generated Files
Scan for gh-guard artifacts:
.github/workflows/*.yml— all workflow filesdeny.toml— cargo-deny configurationrust-toolchain.toml— toolchain pinning.github/dependabot.yml— Dependabot configSECURITY.md— security policyscripts/release.sh— release scriptosv-scanner.toml— OSV scanner config
Report which files are present.
Step 2: YAML Syntax Validation
For each YAML file found:
- Sanitize GitHub Actions
${{ }}expressions (replace with safe placeholders) - Validate YAML structure using
python3 -c 'import yaml; yaml.safe_load(...)'oryq - Report: valid / invalid with error location
Step 3: Workflow Structure Validation
For each GitHub Actions workflow, check:
Required fields:
name:is presenton:trigger is definedpermissions:is set at workflow level- Each job has
runs-on:
SHA pinning:
- All
uses:lines reference a full 40-char SHA (not a tag like@v4) - Exception: SLSA generator (
slsa-github-generator) must use@tag - Version comments are present (e.g.,
# v6.0.2)
Security practices:
persist-credentials: falseon checkout stepsfetch-depth: 0in publish workflow (for ancestry verification)--lockedflag on cargo install commands
Step 4: cargo-deny Validation
If deny.toml exists:
- Run
cargo deny check --hide-inclusion-graph 2>&1(if cargo-deny is installed) - Report any license violations, banned crates, or advisory findings
- If not installed, check TOML syntax validity only
Step 5: Cross-File Consistency
Check relationships between files:
- CI gate job: Does the CI workflow have a gate job with
if: always()andneeds:referencing all other jobs? - MSRV consistency: Does
rust-toolchain.tomlchannel match the MSRV used in CI workflow? - Publish workflow references: If publish workflow references an environment name, note it for user to create
- Fuzz targets: If fuzz workflow exists, does it reference targets that match
fuzz/Cargo.toml[[bin]]entries? - Dependabot ecosystems: Does dependabot.yml cover both
github-actionsandcargo?
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 · 105 lines · 12 tokens per session scan A 5c4db04c9775
verify is a command published in the GitHub repository sbom-tool/gh-guard (15 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 880 once invoked, about $0.0001 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 commands, from other repositories
bob-update
Run the installed Hacker Bob update workflow for this project.
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
scope
Prepare a focused analysis scope for large codebases or monorepos using repomix. Creates a digestible snapshot of the target code for subsequent security analysis.
scan
Run automated static analysis and write the results to .claude/findings.json.
mobile-audit
End-to-end mobile audit driver for Android targets. Most Android bug-bounty work involves a decompiled APK that's been split into two directories.
auto-fix
Automatically generate and apply patches for verified security findings. Uses the patch-advisor agent to create context-aware fixes.