New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vulnerability Validation

by codexstar69 in codexstar69/bug-hunter

Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts.

MITAuto-check passedSecurity

Install Vulnerability Validation

skills CLI
$ npx skills add codexstar69/bug-hunter --skill vulnerability-validation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codexstar69/bug-hunter vulnerability-validation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codexstar69/bug-hunter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vulnerability-validation .claude/skills/vulnerability-validation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vulnerability-validation
GitHub stars
519
Token cost
~497 tokens
SKILL.md length
195 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts.

  • Works in 6 steps: Read the findings and isolate the… → Trace reachability → Trace exploitability → …
  • Wants confirmation that a suspected vulnerability is actually exploitable
  • SKILL.md covers Purpose, Inputs, Workflow and Outputs, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vulnerability Validation is an agent skill from codexstar69/bug-hunter. Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts. Use after security scans, before patch generation, or whenever the user wants confirmation that a suspected vulnerability is actually exploitable.

Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Security review. The repository describes itself as: Adversarial AI bug hunter with auto-fix skill for Claude Code, Cursor, Codex CLI, GitHub Copilot CLI, Kiro CLI, Opencode, Pi Coding Agent, and more. Multi-agent pipeline finds… The licence is MIT.

When your agent uses it

  • Wants confirmation that a suspected vulnerability is actually exploitable
  • Tasks that involve Security review

Example prompts

  • “/vulnerability-validation”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read the findings and isolate the security ones.
  2. Trace reachability
  3. Trace exploitability
  4. Check for mitigations already present in code, framework behavior, or deployment assumptions.
  5. For confirmed HIGH/CRITICAL security bugs, generate
  6. Feed the result back into Bug Hunter-native verdicting.

What it can do on your machine

Read from SKILL.md and the folder at commit 3be6973. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vulnerability Validation loads about 497 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 195 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~497

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codexstar69/bug-hunter at commit 3be6973, republished under its MIT licence (© codexstar69). 195 words, ~497 tokens.

Download SKILL.mdSave it as .claude/skills/vulnerability-validation/SKILL.md (or your agent's skills folder).
name
vulnerability-validation
description
Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts. Use after security scans, before patch generation, or whenever the user wants confirmation that a suspected vulnerability is actually exploitable.

Vulnerability Validation

This is a bundled local Bug Hunter companion skill. It strengthens the security-specific parts of the Skeptic/Referee process.

Purpose

Take suspected or confirmed security findings and answer:

  • Is the vulnerable path reachable?
  • Can an attacker control the input?
  • Are there existing mitigations?
  • How exploitable is it really?
  • What is the CVSS / PoC / impact level?

Inputs

Prefer Bug Hunter-native artifacts:

  • .bug-hunter/hunter-findings.json
  • .bug-hunter/threat-model.md
  • .bug-hunter/security-config.json
  • .bug-hunter/dep-findings.json when dependency issues are involved

Workflow

  1. Read the findings and isolate the security ones.
  2. Trace reachability:
    • EXTERNAL
    • AUTHENTICATED
    • INTERNAL
    • UNREACHABLE
  3. Trace exploitability:
    • EASY
    • MEDIUM
    • HARD
    • NOT_EXPLOITABLE
  4. Check for mitigations already present in code, framework behavior, or deployment assumptions.
  5. For confirmed HIGH/CRITICAL security bugs, generate:
    • exploitation path
    • benign proof of concept
    • CVSS vector + score
  6. Feed the result back into Bug Hunter-native verdicting.

Outputs

When used as a companion to the main pipeline, keep outputs compatible with:

  • .bug-hunter/referee.json
  • .bug-hunter/report.md

If a separate validation artifact is helpful for the run, place it under .bug-hunter/validated-findings.json.

Important constraints

  • This skill validates findings; it does not replace the normal fix pipeline.
  • Keep outputs portable and self-contained under .bug-hunter/.
  • Prefer explicit reasoning for false positives so the user can trust dismissals.

© codexstar69, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/vulnerability-validation of codexstar69/bug-hunter.

Open the folder on GitHubat commit 3be6973

Compare with similar skills

Vulnerability Validation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vulnerability Validation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vulnerability Validation this skillcodexstar69/bug-hunter519—~497Automated safety check: PassMIT
Native Dependency Updatemono/SkiaSharp5.6k—~4.1kAutomated safety check: PassMIT
Skillward AuditFangcun-AI/SkillWard143—~2.9kAutomated safety check: PassCustom licence
Security AuditTheDecipherist/claude-code-mastery550—~1.3kAutomated safety check: NotesMIT
Verification LoopGalaxy-Dawn/claude-scholar5.7k1 repos~888Automated safety check: PassMIT
Review Criteriaromshark/datapages113—~1.2kAutomated safety check: PassMIT

Similar skills

  • Native Dependency Update

    mono/SkiaSharp

    Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.

    5.6k GitHub stars~4.1k tokensUpdated today
    SecurityAuto-check passed

  • Skillward Audit

    Fangcun-AI/SkillWard

    Security-audit a third-party skill bundle (folder with SKILL.md, or .zip / .tar.gz archive) before installing it, using the SkillWard cloud scanner.

    143 GitHub stars~2.9k tokensUpdated 2 mo ago
    SecurityAuto-check passed

  • Security Audit

    TheDecipherist/claude-code-mastery

    Checks a codebase for hardcoded secrets, vulnerable dependencies, weak input handling, weak authentication and unsafe transport settings before deployment or merge.

    550 GitHub stars~1.3k tokensUpdated 5 mo ago
    SecurityAuto-check: notes

  • Verification Loop

    Galaxy-Dawn/claude-scholar

    This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR.

    5.7k GitHub starsUsed in 1 repo~888 tokens
    SecurityAuto-check passed

  • Review Criteria

    romshark/datapages

    Classify Datapages findings by reach and severity and write review-.md reports.

    113 GitHub stars~1.2k tokensUpdated 2 days ago
    SecurityAuto-check passed

  • Architectural Analysis

    pedronauck/skills

    Audit architecture, dead code, duplication, type confusion, and code smells across a codebase.

    633 GitHub starsUsed in 1 repo~524 tokens
    SecurityAuto-check passed

More from codexstar69/bug-hunter

All 11 skills in this repo

  • Bug Hunter

    codexstar69/bug-hunter

    Precision-first adversarial bug hunting for runtime, logic, data, concurrency, and security defects.

    519 GitHub stars~5k tokensUpdated 1 mo ago
    Auto-check passed

  • Commit Security Scan

    codexstar69/bug-hunter

    Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context.

    519 GitHub stars~629 tokensUpdated 1 mo ago
    Auto-check passed

  • Doc Lookup

    codexstar69/bug-hunter

    Unified documentation lookup for Bug Hunter agents. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~592 tokensUpdated 1 mo ago
    Auto-check passed

  • Fixer

    codexstar69/bug-hunter

    Surgical code fixer for Bug Hunter. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Hunter

    codexstar69/bug-hunter

    Deep behavioral code analysis agent for Bug Hunter. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Recon

    codexstar69/bug-hunter

    Codebase reconnaissance agent for Bug Hunter. An agent skill from codexstar69/bug-hunter.

    519 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Vulnerability Validation

What does Vulnerability Validation do?

Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts. Vulnerability Validation is an agent skill from codexstar69/bug-hunter. Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts.

When should I use Vulnerability Validation?

Vulnerability Validation fits situations like: wants confirmation that a suspected vulnerability is actually exploitable; tasks that involve Security review.

How do I install Vulnerability Validation in Claude Code?

Run `npx skills add codexstar69/bug-hunter --skill vulnerability-validation -a claude-code`. Or copy the skill folder (skills/vulnerability-validation in codexstar69/bug-hunter) into .claude/skills/vulnerability-validation in your project. Claude Code loads it when a task matches its description.

How do I install Vulnerability Validation in Codex?

Run `npx skills add codexstar69/bug-hunter --skill vulnerability-validation -a codex`. Or copy the skill folder (skills/vulnerability-validation in codexstar69/bug-hunter) into .agents/skills/vulnerability-validation in your project. Codex loads it when a task matches its description.

Can I use Vulnerability Validation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codexstar69/bug-hunter --skill vulnerability-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vulnerability-validation, .gemini/skills/vulnerability-validation, .github/skills/vulnerability-validation and .opencode/skills/vulnerability-validation in your project.

What does Vulnerability Validation need to run?

SKILL.md names no scripts, command-line tools or credentials: Vulnerability Validation is instructions for the agent only.

Does Vulnerability Validation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vulnerability Validation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vulnerability Validation use?

Vulnerability Validation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vulnerability Validation use?

About 497 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vulnerability Validation?

Skills that share tags, products or a category with Vulnerability Validation: Native Dependency Update (mono/SkiaSharp, 5.6k stars), Skillward Audit (Fangcun-AI/SkillWard, 143 stars), Security Audit (TheDecipherist/claude-code-mastery, 550 stars) and Verification Loop (Galaxy-Dawn/claude-scholar, 5.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vulnerability Validation?

codexstar69 (a GitHub user) maintains it in codexstar69/bug-hunter, which has 519 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 17, 2026.

Source: codexstar69/bug-hunter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.