agentsclimarketplace

Omv radar

Skill bx33661/oh-my-vul/skills/omv-radar

Evidence-first vulnerability research workspace and Skills for Claude Code and Codex.

Install
npx -y skills add bx33661/oh-my-vul --skill omv-radar

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Provides passive watchlist intelligence for oh-my-vul. Use when the user asks what changed for watched packages, ecosystems, vulnerability classes, advisories, releases, or invokes `/omv-radar`. Reads `.omv/radar/watchlist.yaml`, uses only passive external sources or offline fixtures, and writes local radar events for later briefings.

SKILL.md

2.2 KB, as published. Nobody here has run it

omv-radar

Maintain passive intelligence for watched packages and vulnerability classes.

Invocation

/omv-radar refresh [--dry-run]
/omv-radar brief

Workflow

  1. Read .omv/radar/watchlist.yaml.
  2. For refresh, prefer the CLI:
    • omv radar refresh --dry-run for fixture-backed offline validation.
    • omv radar refresh for local event append.
  3. For summaries, run omv radar brief.
  4. Group output by ecosystem, package, and signal type: advisory, release, suspected fix, or watchlist snapshot.
  5. After a successful manual refresh, offer a weekly Monday refresh reminder, but do not create it unless the user asks.

Signal Methodology

Use radar as a triage aid, not as proof of a vulnerability.

  • Advisory signal: compare ecosystem, package identity, affected range, vulnerability class, and referenced fix locations.
  • Release signal: look for security-relevant changelog language, dependency bumps, parser/validation changes, or guard hardening.
  • Suspected-fix signal: treat commit messages such as "validate", "sanitize", "allowlist", or "path check" as review prompts only.
  • Watchlist signal: record that a watched item was evaluated, even when no advisory-like signal appears.

Prioritize review when multiple independent signals point to the same component or guard. Lower priority when only a broad keyword matches.

Passive Boundary

Radar may read advisory databases, registries, and public repository metadata. It must not send requests to target runtime services, run PoCs, or probe package deployments.

Output

End with a concise brief:

  • new advisories or CVEs
  • new releases
  • suspected fix commits
  • audit candidates worth reviewing next

If the watchlist is missing, tell the user to create .omv/radar/watchlist.yaml and include a sanitized example. Do not present any real active vulnerability as a tutorial target.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.