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 HermeticOrmus/LibreSecOps-Claude-Code --skill dependency-risk-assessmentgit 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/skills/hermeticormus/libresecops-claude-code/dependency-risk-assessment)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/dependency-risk-assessment"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/dependency-risk-assessment/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/dependency-risk-assessment"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/dependency-risk-assessment.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.01923 |
| Opus 5.5 | $0.00026 | $0.00769 |
| Sonnet 5.5 | $0.00013 | $0.00385 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
dependency-risk-assessment 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 12d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Risk Assessment
Methodology for scoring and prioritizing dependency risk across vulnerability history, maintainer health, dependency depth, license compatibility, and provenance.
Knowledge Base
Why Risk Scoring Matters
Not all dependency vulnerabilities are equal. A critical CVE in a deeply nested, never-called transitive dependency is lower risk than a medium-severity issue in a direct dependency that processes user input. Risk assessment applies context to raw vulnerability data so teams fix what matters first.
Risk Dimensions
1. Vulnerability Exposure
- Known CVEs (NVD, OSV, GitHub Advisory Database)
- CVSS v3.1 base score (severity of the vulnerability itself)
- EPSS score (probability of exploitation in the next 30 days, based on real-world data)
- CISA KEV status (confirmed active exploitation in the wild)
- Time since disclosure (unpatched for longer = higher risk)
- Patch availability (fix exists but not applied vs. no fix exists)
2. Reachability
- Is the vulnerable function/method actually called by your code?
- Is the vulnerable code path reachable through your application's entry points?
- Does your configuration enable the vulnerable feature?
- Static analysis (call graph) vs. dynamic analysis (runtime tracing)
3. Maintainer Health
- Last commit date (>12 months without activity = concern)
- Number of active maintainers (bus factor)
- Issue and PR response time
- Whether the maintainer has enabled 2FA (npm audit signatures)
- Maintainer account age and reputation
- History of security response (how quickly past CVEs were patched)
4. Dependency Depth and Breadth
- Direct dependency vs. transitive (and how many levels deep)
- Number of downstream dependents (high-value target for attackers)
- Number of own transitive dependencies (larger attack surface)
- Whether the dependency is a build-time-only or runtime dependency
5. License Risk
- Copyleft licenses (GPL, AGPL) in proprietary codebases
- License incompatibility between dependencies
- Missing or ambiguous license declarations
- "UNLICENSED" or custom license terms requiring legal review
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.
- 12d ago Changed · +5 lines · +64 tokens per session 717e912ea05e
- 1mo ago First seen · 189 lines · 0 tokens per session scan A d01f5145cbef
dependency-risk-assessment is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 64 tokens to every session and 1,923 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.