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 sbom-tool/gh-guard --skill dependency-policygit 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/skills/sbom-tool/gh-guard/dependency-policy)<a href="https://agentmods.dev/skills/sbom-tool/gh-guard/dependency-policy"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/dependency-policy.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.1 | $0.00019 | $0.01368 |
| Opus 5 | $0.00010 | $0.00684 |
| Sonnet 5 | $0.00004 | $0.00274 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
dependency-policy 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 7d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Policy for Rust Projects
A robust dependency policy uses three complementary layers: cargo-deny for policy enforcement, Dependabot for automated updates, and osv-scanner for vulnerability detection.
Three-Layer Defense
| Layer | Tool | What It Does | When It Runs |
|---|---|---|---|
| Policy | cargo-deny | Enforce license, ban, source, and advisory rules | CI (every PR) |
| Updates | Dependabot | Auto-create PRs for dependency updates | Weekly |
| Scanning | osv-scanner | Detect known vulnerabilities | CI + scheduled |
Layer 1: cargo-deny
Configuration Sections
[graph] — Define which targets to check:
[graph]
targets = [
"x86_64-unknown-linux-gnu",
"aarch64-apple-darwin",
"x86_64-pc-windows-msvc",
]
all-features = true
[advisories] — Security advisory handling:
[advisories]
unmaintained = "workspace" # or "all"
ignore = [] # Add RUSTSEC IDs to temporarily ignore
[licenses] — License allowlist:
[licenses]
confidence-threshold = 0.93
allow = [
"MIT", "Apache-2.0", "BSD-2-Clause", "BSD-3-Clause",
"ISC", "MPL-2.0", "Unicode-3.0", "CC0-1.0", "Zlib",
]
[bans] — Dependency bans:
[bans]
multiple-versions = "warn" # Warn on duplicate deps (different versions)
wildcards = "deny" # Deny wildcard version requirements
highlight = "all" # Show all duplicates, not just first
deny = [
{ name = "openssl", wrappers = [] }, # Ban openssl
{ name = "openssl-sys", wrappers = [] }, # Ban openssl-sys
]
[sources] — Source origin control:
[sources]
unknown-registry = "deny" # Only allow known registries
unknown-git = "deny" # No git dependencies
allow-registry = ["https://github.com/rust-lang/crates.io-index"]
cargo-deny v0.19 Changes
GOTCHA: cargo-deny v0.19 made breaking changes:
- Removed the
vulnerabilitykey from[advisories] - Use
"all"or"workspace"for unmaintained/unsound checks - The
deny.tomlformat changed — check your version
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.
- 7d ago First seen · 188 lines · 19 tokens per session scan A 7a896f12a81f
dependency-policy is a skill published in the GitHub repository sbom-tool/gh-guard (15 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,368 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 skills, from other repositories
apiiro-mcp-secure-prompt
Use the Apiiro MCP tool apiirosecureprompt when Apiiro MCP is configured in the client and the user wants security guidance added to a coding task before implementation. Trigger on secure-prompt via MCP, or when the user asks for security-aware prompt enhancement before coding (auth, new APIs, persistence, secrets…
implementing-github-advanced-security-for-code-scanning
Configure GitHub Advanced Security with CodeQL to perform automated static analysis and vulnerability detection across repositories at enterprise scale.
bob-egress
List, add, test, enable, disable, or remove Hacker Bob egress profiles from Codex.
detecting-typosquatting-packages
Flag misspelled, brandjacked, and typosquatted package names across npm, PyPI, and crates.io before installation using edit-distance, keyboard-proximity, and known-target corpus matching with typomania, OSSGadget, and pypi-scan.
security-expert
Expert-level application security, OWASP Top 10, penetration testing, and security best practices. Use when the user mentions OWASP, pentesting, appsec, vulnerability, encryption, or authentication, or when the task involves Security Principles, OWASP Top 10, Security Domains, or Broken Access Control.
dependency-check
Audit project dependencies for known-vulnerable versions and risky pinning. Parses requirements.txt and package.json, matches a bundled offline advisory DB, optionally queries OSV.dev live, and warns about unpinned versions. Use when the user asks to "check dependencies for vulnerabilities", "audit my requirements.txt…