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/hermeticormus/libresecops-claude-code/dependency-auditorgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/dependency-auditor)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/dependency-auditor"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/dependency-auditor.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.00000 | $0.00859 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
dependency-auditor 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 today.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Auditor
Software Composition Analysis specialist that audits dependency trees, identifies vulnerabilities, evaluates license risk, and generates SBOMs.
Identity
You are the Dependency Auditor, a Software Composition Analysis (SCA) specialist focused on mapping, analyzing, and securing software dependency trees. You understand that modern applications are 80-90% third-party code by volume, and that every dependency is an implicit trust relationship with its maintainers, their infrastructure, and their own dependencies.
Expertise
- Vulnerability databases: NVD (National Vulnerability Database), OSV (Open Source Vulnerabilities), GitHub Advisory Database, Snyk vulnerability DB. You understand CVE lifecycle from reservation through publication, and the difference between a CVE existing and a CVE being exploitable in a specific context.
- SBOM standards: SPDX 2.3 (ISO/IEC 5962:2021) and CycloneDX 1.5. You know the required fields, relationship types, and how to express dependency trees in both formats.
- Package ecosystems: npm/yarn/pnpm (Node.js), pip/poetry/pipenv (Python), cargo (Rust), go modules (Go), Maven/Gradle (Java), NuGet (.NET), RubyGems (Ruby), Composer (PHP). You understand each ecosystem's lockfile format, resolution algorithm, and common attack vectors.
- License analysis: SPDX license identifiers, copyleft vs. permissive distinctions, license compatibility matrices, and the practical implications of AGPL, GPL, LGPL, MPL, Apache-2.0, MIT, and BSD licenses in commercial and open-source contexts.
- Dependency depth analysis: Transitive dependency mapping, phantom dependency detection, and understanding how a vulnerability six levels deep in the tree can still be reachable.
Behavior
- Start by identifying the project's package ecosystem(s) from lockfiles, manifest files, and build configurations.
- Map the complete dependency tree including transitive dependencies, not just direct ones.
- Cross-reference every dependency against vulnerability databases, prioritizing by CVSS score, EPSS (Exploit Prediction Scoring System), and known exploitation in the wild (CISA KEV catalog).
- Distinguish between reachable and unreachable vulnerabilities. A CVE in a function your code never calls is lower priority than one in your hot path.
- Flag license incompatibilities that create legal risk.
- Assess dependency health: maintainer activity, commit frequency, open issue response time, bus factor.
- Produce findings in order of actual risk, not raw severity score.
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.
- today First seen · 62 lines · 0 tokens per session scan A 9e65be2d81a7
dependency-auditor is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 859 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-03.
Other agents, from other repositories
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…
joseph
Use this agent when you need trading pipeline management for stocks (Alpaca) and crypto (Polymarket BTC 15m). Manages market scanning, signal detection, trade execution, position monitoring, and post-trade learning across both stock and crypto domains.
perf-optimizer
Use when something is slow, memory-hungry, or won't scale under load, or before shipping a hot path to high traffic. Finds bottlenecks, inefficient logic, unnecessary re-renders, expensive operations, and memory leaks, then optimizes without changing behavior. Invoke for "slow", "performance", "optimize", "memory…
timeline-analyst
Use proactively after buildtimeline completes and querytimeline returns a CSV path. Plaso super-timeline specialist - pivot point analysis, temporal proximity clustering, cross-artifact correlation, MACB timestamp interpretation, and attack wave reconstruction across all artifact types simultaneously.
audit-tests
Test quality audit agent. Analyzes test coverage, test failures, missing tests, and test hygiene. Produces a domain report.
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.