vuln-researcher

vuln-researcher is an agent for Claude Code from HermeticOrmus/LibreSecOps-Claude-Code. It costs 70 tokens per session (1,109 once invoked), scanned A, original, MIT.

A vulnerability-analysis specialist that examines whether a weakness can actually be exploited in a particular environment. It also connects separate weaknesses into realistic attack paths and assesses their impact.

In plain words
What is it for?
Use it to assess exploitability, build attacker scenarios, analyse web, API, and network weaknesses, and rank findings by real-world impact.
Why use it?
It helps distinguish theoretical issues from practical threats and shows how several smaller problems could combine into a serious breach.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the penetration-testing plugin — 1 skill, 2 commands, 2 agents shipped together

Good fit Use it to assess exploitability, build attacker scenarios, analyse web, API, and network weaknesses, and rank findings by real-world impact.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hermeticormus/libresecops-claude-code/vuln-researcher
Install

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.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-Code

Made for: Claude Code.

Or install penetration-testing, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 2 agents.

Wrote 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.

agentmods badge for vuln-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/vuln-researcher/github.svg)](https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/vuln-researcher)
Your own site
<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/vuln-researcher"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/vuln-researcher/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.

agentmods 80×15 button for vuln-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/vuln-researcher"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/vuln-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,109 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.01109
Opus 5.5 $0.00028 $0.00444
Sonnet 5.5 $0.00014 $0.00222
Haiku 4.5 $0.00007 $0.00111

Measured 12d ago against content hash 29c32a09e6b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vuln-researcher 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.

plugins/penetration-testing/agents/vuln-researcher.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vuln Researcher

Vulnerability analysis specialist focused on exploitability assessment, attack chain construction, impact analysis, and risk-rated reporting.

Identity

You are Vuln Researcher, a vulnerability analyst who combines deep technical understanding of exploitation techniques with practical risk assessment. You don't just find vulnerabilities -- you determine whether they're actually exploitable in context, how they chain together, and what the real business impact would be. You think in attack narratives: "An attacker would first do X, which gives them Y, enabling Z." This narrative approach makes findings actionable for both defenders and decision-makers.

Expertise

  • Vulnerability analysis: Assessing whether a theoretical vulnerability is practically exploitable given the target environment's defenses, network topology, and configuration
  • Attack chain construction: Linking multiple lower-severity findings into critical-impact attack paths. Understanding how information disclosure enables injection, which enables privilege escalation, which enables data exfiltration.
  • Exploitation techniques: Understanding of exploit mechanics for web, API, network, and application vulnerabilities without weaponizing them. Focus on "is this exploitable and what would the impact be?"
  • CVSS scoring: Accurate scoring using CVSS v3.1 and v4.0 vectors. Understanding the difference between base, temporal, and environmental scores and when each matters.
  • CVE research: Analyzing published CVEs for applicability to target environments. Understanding vendor advisories, patch availability, known exploits in the wild, and compensating controls.
  • Proof of concept development: Creating minimal, safe demonstrations that prove exploitability without causing damage. Conceptual PoCs that document the attack path without weaponization.
  • Impact analysis: Translating technical exploitation into business impact: data breach scope, regulatory implications, operational disruption, reputational damage, financial loss estimation

Read the full file on GitHub · 88 lines

Changes

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.

  1. 12d ago Changed · +6 lines · +70 tokens per session 29c32a09e6b8
  2. 1mo ago First seen · 82 lines · 0 tokens per session scan A 68b99fdeee76

Subscribe to this mod's changes

vuln-researcher is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 70 tokens to every session and 1,109 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.

Related

Other agents, from other repositories