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/auditgit 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/audit)<a href="https://agentmods.dev/commands/sbom-tool/gh-guard/audit"><img src="https://agentmods.dev/badge/commands/sbom-tool/gh-guard/audit.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.00014 | $0.01285 |
| Opus 5 | $0.00007 | $0.00642 |
| Sonnet 5 | $0.00003 | $0.00257 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
audit 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 4d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit — Supply Chain Security Gap Analysis
Scan the current Rust project and produce a structured gap analysis against CI/CD supply chain best practices.
Workflow
Step 1: Discover Project Context
Read these files to understand the project:
Cargo.toml— crate name, version, MSRV (rust-version), licenserust-toolchain.toml— pinned toolchain version.git/configor rungit remote get-url origin— repo owner/name
Step 2: Check for Expected Files
Check for the presence of each file. For each, report: present/missing/partial.
| Category | Expected File | Location |
|---|---|---|
| CI Pipeline | CI workflow | .github/workflows/ (any file with cargo test) |
| CI Pipeline | Gate job | CI workflow with if: always() + needs: pattern |
| Publishing | Publish workflow | .github/workflows/ (triggered by tags: ["v*"]) |
| Publishing | Trusted Publishing | Publish workflow with crates-io-auth-action |
| Publishing | Workspace publish ordering | Publish workflow handles all publishable crates in dependency order (workspace only) |
| Provenance | SLSA provenance | Publish workflow with slsa-github-generator |
| Provenance | GitHub Release | Publish workflow with gh release create |
| Security | SECURITY.md |
Root or .github/ |
| Security | CodeQL workflow | .github/workflows/ with codeql-action |
| Security | Scorecard workflow | .github/workflows/ with scorecard-action |
| Dependencies | deny.toml |
Root |
| Dependencies | dependabot.yml OR Renovate config |
.github/dependabot.yml OR renovate.json / .github/renovate.json |
| Dependencies | osv-scanner.toml |
Root |
| Toolchain | rust-toolchain.toml |
Root |
| Toolchain | Cargo.lock |
Root (should be committed for binaries/apps) |
| Testing | Fuzz targets | fuzz/ directory |
| Testing | Fuzz workflow OR OSS-Fuzz | .github/workflows/ with cargo-fuzz, OR project listed in google/oss-fuzz |
| Release | Release script | scripts/release.sh or similar |
| License | LICENSE |
Root |
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.
- 4d ago First seen · 132 lines · 14 tokens per session scan A 4d91394e79db
audit is a command published in the GitHub repository sbom-tool/gh-guard (15 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 1,285 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.