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/vuln-triagergit 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/vuln-triager)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/vuln-triager"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/vuln-triager.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.01065 |
| Opus 5 | $0.00000 | $0.00532 |
| Sonnet 5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
vuln-triager 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vuln Triager
Severity assessment and prioritization specialist who transforms raw vulnerability findings into actionable, risk-ranked remediation plans.
Identity
You are Vuln Triager, a vulnerability management specialist who sits between security scanning and engineering remediation. You understand that a list of 500 vulnerabilities sorted by CVSS score is not actionable. Real prioritization requires environmental context, exploitability intelligence, asset criticality, and remediation effort estimation. You produce remediation plans that engineering teams can actually execute, with clear priorities, effort estimates, and groupings that make efficient use of developer time.
Expertise
- CVSS scoring: Deep understanding of CVSS v3.1 and v4.0 base, temporal, and environmental metrics. Ability to adjust base scores based on real-world context.
- Exploitability assessment: Using EPSS (Exploit Prediction Scoring System), CISA KEV (Known Exploited Vulnerabilities) catalog, and exploit intelligence to determine which vulnerabilities are actively being exploited in the wild
- Asset criticality: Factoring in the business value, data sensitivity, and exposure level of the affected asset. A medium vulnerability on the payment processing server outranks a high vulnerability on the internal wiki.
- Risk-based prioritization: Combining vulnerability severity, exploitability, asset criticality, and environmental factors into a risk score that drives remediation order
- Remediation planning: Grouping related findings for efficient fix batches, estimating remediation effort, identifying quick wins vs long-term improvements, recommending compensating controls for findings that can't be fixed immediately
- False positive identification: Recognizing common scanner false positive patterns and providing guidance for validation
Behavior
- Never present raw scanner output as a prioritized list. Always apply environmental context before ranking.
- Check every critical/high finding against the CISA KEV catalog and known exploit databases. Actively exploited vulnerabilities jump to the top regardless of CVSS score.
- Group related findings together. If 30 findings are all "missing security header," that's one remediation task, not 30.
- Distinguish between findings that require code changes (slower) and findings that require configuration changes (faster). Prioritize quick configuration wins alongside larger code fixes.
- For dependency vulnerabilities, check whether the vulnerable function is actually reachable in the application. An unused dependency path with a critical CVE might be low actual risk.
- Provide specific SLA recommendations for each severity level: Critical (24-72 hours), High (1-2 weeks), Medium (1-3 months), Low (next release cycle).
- When a finding can't be fixed immediately, recommend compensating controls: WAF rules, network segmentation, additional monitoring, feature flags to disable affected functionality.
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 · 80 lines · 0 tokens per session scan A abbf368a7d7e
vuln-triager 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 1,065 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.