cve-hunt-benchmark-harness

cve-hunt-benchmark-harness is a skill for Claude Code, Codex from Miosa-osa/OSA. It costs 124 tokens per session (1,218 once invoked), scanned A, original, Apache-2.0.

A benchmark system for testing how well vulnerability-finding tools discover known security flaws. It compares findings with a record of the real vulnerabilities and measures correct findings, missed flaws, false alarms, and time to discovery.

In plain words
What is it for?
It is for creating vulnerability challenges, scoring security findings, and testing whether a tool finds real flaws without reporting too many clean cases as vulnerable.
Why use it?
It provides a consistent way to compare vulnerability-hunting results instead of judging them by anecdotal examples.

Skill for Claude CodeCodex

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

Good fit It is for creating vulnerability challenges, scoring security findings, and testing whether a tool finds real flaws without reporting too many clean cases as vulnerable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/miosa-osa/osa/cve-hunt-benchmark-harness
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 Miosa-osa/OSA --skill cve-hunt-benchmark-harness
Clone the repo
git clone --depth 1 https://github.com/Miosa-osa/OSA

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 cve-hunt-benchmark-harness

README.md
[![agentmods](https://agentmods.dev/badge/skills/miosa-osa/osa/cve-hunt-benchmark-harness/github.svg)](https://agentmods.dev/skills/miosa-osa/osa/cve-hunt-benchmark-harness)
Your own site
<a href="https://agentmods.dev/skills/miosa-osa/osa/cve-hunt-benchmark-harness"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/cve-hunt-benchmark-harness/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 cve-hunt-benchmark-harness

Your own site · 80×15
<a href="https://agentmods.dev/skills/miosa-osa/osa/cve-hunt-benchmark-harness"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/cve-hunt-benchmark-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,218 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.
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.00124 $0.01218
Opus 5.5 $0.00050 $0.00487
Sonnet 5.5 $0.00025 $0.00244
Haiku 4.5 $0.00012 $0.00122

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

Security

Grade A, and why

cve-hunt-benchmark-harness 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.

priv/skills/cve-hunt-benchmark-harness/SKILL.md · 111 lines

How it starts

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

CVE-Hunt Benchmark Harness

Derived from T3MP3ST's src/benchmark/index.ts and bench/ corpora (Apache-2.0). The point of a ground-truth benchmark: measure finding quality — precision AND recall — instead of counting scanner output.

1. Challenge definition

A benchmark challenge bundles everything needed to score a hunt:

id, name, description, difficulty(easy|medium|hard|expert),
target{address, type, zone},
tasks[{name, description, phase, operatorType, priority}],
groundTruth[{id, title, severity, category, matchKeywords[], points}],
timeLimitSec
  • groundTruth is the answer key: every KNOWN vulnerability in the target with its severity, category, matchKeywords (what a correct finding should mention), and a points value.
  • tasks defines the hunting workflow phases so runs are comparable.
  • timeLimitSec bounds the run — time-to-finding is a scored metric.

2. Scoring — precision, recall, F1

For a run that produced findings[] against groundTruth[]:

  • A finding matches a ground-truth vuln when it hits the vuln's matchKeywords (keyword containment over the finding's title/description/category).
  • truePositives = findings that matched ≥1 ground-truth vuln.
  • falsePositives = findings that matched nothing.
  • precision = TP / (TP + FP) — how trustworthy the tool's output is.
  • recall = matched_ground_truth / total_ground_truth — how much was found.
  • f1 = 2 * precision * recall / (precision + recall).
  • pointsScored sums matched vulns' points; report scorePercent against maxPoints.
  • timeToFirstFinding = seconds until the first valid finding; also report findingsPerMinute and totalDurationSec.

Severity breakdown: per severity, {found, total} — a tool that finds all the lows but none of the criticals is not done.

3. Decoys — measuring the false-positive rate honestly

Include CLEAN samples in the corpus (T3MP3ST's DECOY-clean-c, DECOY-clean-java pattern): code that LOOKS vulnerable but is not. Findings against decoys are false positives by construction. A hunter that scores well on vulnerable samples but flags decoys is pattern-matching, not analyzing — and the decoy FP rate is the number that proves it.

Read the full file on GitHub · 111 lines

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 · 111 lines · 124 tokens per session scan A d1d19dae2b47

Subscribe to this mod's changes

cve-hunt-benchmark-harness is a skill published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 11d ago), licensed Apache-2.0. It adds 124 tokens to every session and 1,218 once invoked, about $0.0005 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-09-14.