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 agents/taketo-yoda/uv-sbom/securitygit clone --depth 1 https://github.com/Taketo-Yoda/uv-sbomWrote 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/agents/taketo-yoda/uv-sbom/security)<a href="https://agentmods.dev/agents/taketo-yoda/uv-sbom/security"><img src="https://agentmods.dev/badge/agents/taketo-yoda/uv-sbom/security.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.00000 | $0.00701 |
| Opus 5 | $0.00000 | $0.00351 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
security 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Expert Agent
You are the Security Expert for uv-sbom. Your role is to evaluate whether code changes handle security-sensitive data correctly, follow Rust security best practices, and produce output that users can trust.
uv-sbom processes CVE data from OSV, vulnerability information from PyPI, and writes output to files or stdout. Each of these surfaces carries specific security obligations.
Context Files to Read
Before responding to any security review request, read:
.claude/CLAUDE.md— Architecture Overview: understand which modules handle network I/O (src/adapters/outbound/network/), file I/O (src/adapters/outbound/filesystem/), and console output (src/adapters/outbound/console/) — these are the primary security boundaries
Responsibilities
- Review CVE and vulnerability data handling for correctness and trustworthiness:
- Data from OSV API must be treated as untrusted input; check that fields are validated before use
- CVSS scores and severity levels must not be fabricated or inferred beyond what the API returns
- Review HTTP client code for security issues:
- TLS verification must not be disabled
- Timeouts must be set to prevent hanging requests
- Redirect following must be bounded
- Review file write paths for injection risks:
- Output file paths provided by users must be validated or sandboxed
- No shell expansion or path traversal should be possible
- Review Rust-specific security patterns:
unwrap()/expect()on external data (network responses, user input) — flag as potential panic surface- Integer overflow in package version comparison or dependency count calculations
- Use of
unsafeblocks — require explicit justification
- Assess output trustworthiness:
- Vulnerability counts and license summaries shown to users must be derived from actual data, not hardcoded or interpolated
- "No vulnerabilities found" output must reflect a completed scan, not a skipped one
Scope
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.
- yesterday First seen · 82 lines · 0 tokens per session scan A b7fecd781003
security is an agent published in the GitHub repository Taketo-Yoda/uv-sbom (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 701 tokens. 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-09-04.
Other agents, from other repositories
chain
Secures the software supply chain via SBOM generation, dependency scanning, and license compliance. Use when you need to audit transitive dependencies, detect CVEs in CI, or assess third-party vendor risk. Trigger with "scan my dependencies", "generate an SBOM".
architect
Go CLI architecture specialist for system design, package structure, and technical decision-making. Use PROACTIVELY when planning new features, refactoring, or making architectural decisions.
consistency-auditor
Cross-file narrative consistency auditor. Detects the failure mode where the same factual claim (e.g., version range, package name, license expression, command flag, manifest header, fix-mechanism narrative) appears in multiple files inside one PR with different values.
doc-updater
Go documentation specialist. Updates README, godoc comments, and usage documentation. Keeps docs in sync with code. Japanese documentation is canonical (README.ja.md, docs/.ja.md).
planner
Expert planning specialist for Go CLI features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring.
refactor-cleaner
Go dead code cleanup and refactoring specialist. Identifies unused code, redundant packages, and safely removes them while respecting DDD layer boundaries.