A skill for turning one confirmed security bug into a disclosure-ready GitHub advisory. The report includes the cause, proof that the bug works, its impact, and supporting source evidence.

Writing a single vulnerability report with reproduction details, affected behavior, trust assumptions, impact, code evidence, and links to relevant files or fixes.

It helps present an established vulnerability clearly to maintainers or security teams. It is for reporting a known finding, not for discovering or testing whether one exists.

vuln-report — Skill for Claude Code by waybarrios/opencode-power-pack

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.

Any agent

npx skills add waybarrios/opencode-power-pack --skill vuln-report

Clone the repo

git clone --depth 1 https://github.com/waybarrios/opencode-power-pack

Made for: Claude Code.

Or install opencode-power-pack, the plugin that ships this one along with the rest of its 55 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/waybarrios/opencode-power-pack/vuln-report/github.svg)](https://agentmods.dev/skills/waybarrios/opencode-power-pack/vuln-report)

Your own site

<a href="https://agentmods.dev/skills/waybarrios/opencode-power-pack/vuln-report"><img src="https://agentmods.dev/badge/skills/waybarrios/opencode-power-pack/vuln-report/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/waybarrios/opencode-power-pack/vuln-report"><img src="https://agentmods.dev/badge/skills/waybarrios/opencode-power-pack/vuln-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,560 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.01560
Opus 5.5	$0.00018	$0.00624
Sonnet 5.5	$0.00009	$0.00312
Haiku 4.5	$0.00004	$0.00156

Measured 1mo ago against content hash cba9f739f3eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vuln-report 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

vuln-report — 91% identical, 5 lines differ

skills/vuln-report/SKILL.md · 117 lines

How it starts

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

Vulnerability Report

Overview

Draft one disclosure-ready report for one confirmed bug. Keep the report evidence-driven, concrete, and concise. Prefer the section order and phrasing rules in references/report-template.md.

Workflow

Confirm the report is about one bug only.
Extract the minimum facts needed to prove the issue:
- vulnerable component or behavior
- attacker-controlled input or missing validation
- preconditions and trust boundary
- exploit result
- practical impact
- strongest reproduction path
- decisive source locations and any relevant fix commit
Separate demonstrated facts from inference. State assumptions explicitly.
Draft the report using the required section order from references/report-template.md.
Always embed at least one fenced code snippet from the decisive code path, and explain what each snippet proves.
Always convert repository file references and patch references into GitHub markdown links, and prefer embedding those links directly into the surrounding explanation instead of listing them separately.
Add only the optional sections that materially improve accuracy or triage value.
Save the final report as report.md inside a folder named with the bug's severity identifier (C1, H1, M1, etc.) followed by a lowercase hyphenated slug derived from the final report title. Use C for Critical, H for High, M for Medium, sequentially numbered if there are multiple bugs of the same severity. Example: C1-cross-site-websocket-hijacking-re-enabled-by-allow-websocket/report.md. Also, ensure the bug report title and internal references use this ID (e.g., '[C1] Cross-Site WebSocket Hijacking'). Do not write reports for Low severity findings — document them in the summary table only.
Remove filler, hedging, and unproven claims before finalizing.

Required Sections

Always include these sections in this order:

Summary
Details
Root Cause
Proof of Concept (PoC)
Impact

Read the full file on GitHub · 117 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/report-template.md 4.1 KB

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.

1mo ago First seen · 117 lines · 44 tokens per session scan A cba9f739f3eb

Subscribe to this mod's changes

vuln-report is a skill published in the GitHub repository waybarrios/opencode-power-pack (544 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 1,560 once invoked, about $0.0002 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-08-30.

Claude Code Code review Debugging Security ai-agents anthropic developer-tools llm-tools

vercel-agent

Vercel Agent guidance — AI-powered code review, incident investigation, and SDK installation. Automates PR analysis and anomaly debugging. Use when configuring or understanding Vercel's AI development tools.

build-with-dhiraj/ai-workflow-framework-portability-kit · 43 tokens

oracle

Oracle second-model review: bundle prompts/files, debug, refactor, design.

steipete/oracle · 18 tokens

code-review-web

Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…

rampstackco/claude-skills · 121 tokens

vuln-report