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.
git 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/commands/hermeticormus/libresecops-claude-code/vuln-triage)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/vuln-triage"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/vuln-triage/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/commands/hermeticormus/libresecops-claude-code/vuln-triage"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/vuln-triage.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.00021 | $0.00943 |
| Opus 5.5 | $0.00008 | $0.00377 |
| Sonnet 5.5 | $0.00004 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
vuln-triage 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vuln-triage
Prioritize vulnerability findings into an actionable remediation plan based on risk, exploitability, asset criticality, and effort.
Trigger
Use this command when:
- You have scan results that need prioritization for engineering teams
- A large backlog of vulnerabilities needs to be organized into a remediation plan
- Stakeholders need a risk-based view of vulnerability findings
- You need to determine which vulnerabilities to fix first given limited resources
Input
Required:
- Findings: Scan results, vulnerability list, or description of discovered vulnerabilities
Optional:
- Asset context: Description of the affected system's business criticality, data sensitivity, and exposure level
- Constraints: Available remediation time, team capacity, upcoming release deadlines
- Risk appetite: Organization's tolerance for risk (
low= fix everything,medium= focus on high+critical,high= only actively exploited)
Process
Step 1: Finding Normalization
- Standardize all findings to a consistent format with CVSS base score, CWE, and CVE where applicable
- Remove exact duplicates and merge related findings
- Validate severity ratings -- re-score if scanner ratings seem inaccurate
Step 2: Contextual Risk Assessment
For each finding, assess:
-
Exploitability
- Is there a known public exploit? (Check Exploit-DB, Metasploit, Nuclei templates)
- Is it in the CISA KEV catalog? (Confirmed actively exploited)
- What is the EPSS score? (Probability of exploitation in next 30 days)
- What is the attack complexity? (Network-accessible vs requires local access)
-
Asset Criticality
- What data does the affected system handle? (PII, financial, health, public)
- What is the system's exposure? (Internet-facing, internal, airgapped)
- What is the business impact of compromise? (Revenue, reputation, regulatory)
- How many users are affected?
-
Environmental Factors
- Are there compensating controls? (WAF, network segmentation, monitoring)
- Is the vulnerable function actually reachable/used?
- Is the system scheduled for decommission?
- Are there dependencies that must be fixed first?
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 · +21 tokens per session 2249483508f0
- 1mo ago First seen · 106 lines · 0 tokens per session scan A 7e67eac542e7
vuln-triage is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 943 once invoked, about $0.0001 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 commands, from other repositories
verify
An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.
corporate-launcher
Build a secure, branded, organization-specific launcher around an AI coding CLI (Claude Code, Codex CLI, Gemini CLI, Cursor, or Cline) so the user can.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.