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 vuln-report-writinggit 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/vuln-report-writing)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/vuln-report-writing"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/vuln-report-writing/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/vuln-report-writing"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/vuln-report-writing.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.00000 | $0.02095 |
| Opus 5 | $0.00000 | $0.01047 |
| Sonnet 5 | $0.00000 | $0.00419 |
| Haiku 4.5 | $0.00000 | $0.00210 |
Grade C, and why
vuln-report-writing scanned grade C with 2 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 9d 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.
Cloud metadata endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- "SSRF via PDF export feature allows access to internal AWS metadata (169.254.169.254) from pdf.example.com" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For findings that require specific timing or automation, provide a minimal proof-of-concept script. Include comments explaining each step. Use common languages (Python, curl, JavaScript). How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vuln Report Writing
Guide to writing vulnerability reports that get accepted, triaged quickly, and rewarded fairly, with templates, CVSS guidance, and common pitfalls.
Knowledge Base
Why Report Quality Matters
A triage analyst typically handles 50-100+ reports per day. They spend approximately 5 minutes on initial assessment. Your report must communicate the vulnerability's existence, impact, and reproduction method in that time. Reports that require back-and-forth clarification take weeks to resolve instead of days.
Report quality directly affects:
- Acceptance rate: Clear reports with reproduction steps get accepted. Vague reports get closed as "informative"
- Triage speed: Well-structured reports are triaged in days. Poor reports sit in queues for weeks
- Bounty amount: Impact clarity and severity accuracy influence reward decisions
- Reputation: Consistent quality builds reputation, leading to private program invitations
Title Writing
The title is the single most important line. It appears in triage queues, dashboards, and email notifications.
Formula: [Vulnerability Type] in [Location/Feature] allows [Impact] on [Asset]
Good titles:
- "Stored XSS via Markdown rendering in comment system allows session cookie theft on app.example.com"
- "IDOR in /api/v2/orders/{id} allows any authenticated user to view other users' order details including payment information"
- "SSRF via PDF export feature allows access to internal AWS metadata (169.254.169.254) from pdf.example.com"
- "Race condition in coupon redemption allows unlimited use of single-use promotional codes"
Bad titles:
- "XSS" (no location, no impact)
- "Security issue found" (meaningless)
- "Critical vulnerability" (no information)
- "Multiple issues in example.com" (split into separate reports)
CVSS v3.1 Scoring Guide
Common web vulnerability scores:
| Vulnerability | Typical CVSS | Vector | Notes |
|---|---|---|---|
| Unauthenticated RCE | 9.8 | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | Network, no auth, no interaction |
| Unauthenticated SQLi (data access) | 9.1 | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | Read + write database |
| Stored XSS (admin context) | 8.4 | AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N | Scope changed, user interaction |
| SSRF to internal services | 7.5-9.1 | Varies | Depends on what is accessible |
| IDOR (read sensitive data) | 6.5 | AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | Auth required, high confidentiality |
| Reflected XSS | 6.1 | AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | Scope changed, user interaction |
| Open redirect | 4.7 | AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N | Low impact alone, chains well |
| Information disclosure (minor) | 4.3 | AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N | Low confidentiality impact |
| Missing security header | 0-4.0 | Varies | Usually informational |
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.
- 9d ago First seen · 164 lines · 0 tokens per session scan C 8f2ca74eacbd
vuln-report-writing is a skill 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 2,095 tokens. A static security scan graded it C with 2 findings (cloud metadata endpoint, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.