Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Vulnerability Report · waybarrios | DecimalAI

securityby waybarrios

Vulnerability Report

waybarrios/vuln-report

Source waybarrios/opencode-power-pack ↗License MIT

Draft a single-vulnerability report in GitHub advisory style from an audit finding, bug note, patch diff, PoC, or code review evidence.

SkillScore73Maintained

Automatic

Security & AppSec pack

Last verified 8/19/2026

What it changes

Passed 16 of 22 test cases with the skill, and 7 of 22 without it.

Without skill32%

With skill73%

Checks it passed that the model alone missed

The report title begins with '[M1]'.
The document title includes the prefix '[C1]'.
The destination folder path starts with 'H1-'.

and 9 more in the full report

9 fixed7 passed either way6 still failing0 broke

Pass-rate lift: +41 pp
Tokens: +121%
Agent turns: 0%
Response time: +31%

Model gemini-3.6-flashMeasured 8/19/2026v116 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/waybarrios-vuln-report/SKILL.md https://app.decimal.ai/s/waybarrios-vuln-report/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add waybarrios-vuln-report, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/waybarrios-vuln-report/ and pins it in .decimal/skills.lock

decimalai skills add waybarrios-vuln-report

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/waybarrios-vuln-report/SKILL.md https://app.decimal.ai/s/waybarrios-vuln-report/SKILL.md

Raw file: /s/waybarrios-vuln-report/SKILL.md ↗ · machine-readable summary at /s/waybarrios-vuln-report.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 9

Prompt

We have two High severity findings to report: an authentication bypass in `auth.py` and a privilege escalation in `admin.py`. How should their report folder names and titles be prefixed?

What was checked, without and with the skill
Checked	Without skill	With skill
The second High severity finding is assigned the prefix '[H2]'.	Missed	Passed

case-17 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md110 lines2 files

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

If the repository already uses Technical Details with Root Cause nested under it, preserve that local pattern. Otherwise keep Root Cause as its own section.

Evidence Rules

Include one or more fenced code snippets in the report, usually in Details or Root Cause.

Track record

Benchmark

16 / 22

test cases passed, vs 7 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

waybarrios / opencode-power-pack

skills/vuln-report/SKILL.md

View on GitHub ↗

License MIT (modified; see UPSTREAMS.json)Imported 8/17/2026Version v1Bundled 1 file

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Vulnerability Report

Overview

Workflow

Required Sections

Evidence Rules

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills