agentmods.dev

vulnerability-validation

vulnerability-validation is a skill for Claude Code, Codex from codexstar69/bug-hunter. It costs 49 tokens per session (436 once invoked), scanned A, original, MIT.

A security review step that checks whether a suspected vulnerability can actually be reached and exploited. It uses security scan results and related project files to assess attacker control, existing protections, severity, and impact.

In plain words
What is it for?
Use it after a security scan, before creating a patch, or when you need to confirm a suspected vulnerability. For confirmed severe issues, it records the attack path, a safe proof of concept, and a CVSS severity assessment.
Why use it?
Security scanners can report problems that are unreachable or already protected. This step helps distinguish real, exploitable vulnerabilities from false alarms.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 524repo +3 2mo ago A scan SkillSpector: pass 49 tokens original MIT

Good fit Use it after a security scan, before creating a patch, or when you need to confirm a suspected vulnerability. For confirmed severe issues, it records the attack path, a safe proof of concept, and a CVSS severity assessment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/codexstar69/bug-hunter/vulnerability-validation
View source ↗ codexstar69/bug-hunter
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 codexstar69/bug-hunter --skill vulnerability-validation
Clone the repo
git clone --depth 1 https://github.com/codexstar69/bug-hunter

Made for: Claude Code, Codex.

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 vulnerability-validation

README.md
[![agentmods](https://agentmods.dev/badge/skills/codexstar69/bug-hunter/vulnerability-validation/github.svg)](https://agentmods.dev/skills/codexstar69/bug-hunter/vulnerability-validation)
Your own site
<a href="https://agentmods.dev/skills/codexstar69/bug-hunter/vulnerability-validation"><img src="https://agentmods.dev/badge/skills/codexstar69/bug-hunter/vulnerability-validation/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 vulnerability-validation

Your own site · 80×15
<a href="https://agentmods.dev/skills/codexstar69/bug-hunter/vulnerability-validation"><img src="https://agentmods.dev/badge/skills/codexstar69/bug-hunter/vulnerability-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 436 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.00436
Opus 5.5 $0.00020 $0.00174
Sonnet 5.5 $0.00010 $0.00087
Haiku 4.5 $0.00005 $0.00044

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

Security

Grade A, and why

vulnerability-validation 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.

skills/vulnerability-validation/SKILL.md · 60 lines

What it actually says

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.
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. 1mo ago First seen · 60 lines · 49 tokens per session scan A 407a867e1587

Subscribe to this mod's changes

vulnerability-validation is a skill published in the GitHub repository codexstar69/bug-hunter (524 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 436 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 CodeSecurityadversarial-aiai-code-reviewauto-fixbug detectionclaude
Related

Other skills, from other repositories

logic-review

Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…

hyhmrright/logic-lens · 161 tokens

logic-fix-all

Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…

hyhmrright/logic-lens · 211 tokens

logic-health

Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…

hyhmrright/logic-lens · 180 tokens

run-iteration-eval

Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…

hyhmrright/logic-lens · 108 tokens

new-skill

Scaffold a new logic- skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is missed. Use when adding a seventh (or later) skill to Logic-Lens.

hyhmrright/logic-lens · 50 tokens

sync-skill-cache

Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills//SKILL.md or guide/shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is…

hyhmrright/logic-lens · 103 tokens