agentmods.dev

omv-critic

omv-critic is a skill for Claude Code, Codex from bx33661/oh-my-vul. It costs 83 tokens per session (982 once invoked), scanned A, original, MIT.

A critical review step for a documented security finding before it is submitted. It checks both the evidence and the likelihood that a vulnerability coordinator or package maintainer will reject the report.

In plain words
What is it for?
Assigning low, medium, or high rejection risk, identifying likely rejection reasons, and recommending a suitable reporting goal such as VulDB, CVE, or GHSA.
Why use it?
It exposes weak proof, duplicate findings, unsupported impact claims, and missing version details before submission. This helps researchers strengthen a report while changes are still possible.

Skill for Claude CodeCodex

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

not rated 4repo 22d ago A scan 83 tokens original MIT

Good fit Assigning low, medium, or high rejection risk, identifying likely rejection reasons, and recommending a suitable reporting goal such as VulDB, CVE, or GHSA.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bx33661/oh-my-vul/omv-critic
View source ↗ bx33661/oh-my-vul npmjs.com
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 bx33661/oh-my-vul --skill omv-critic
Clone the repo
git clone --depth 1 https://github.com/bx33661/oh-my-vul

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 omv-critic

README.md
[![agentmods](https://agentmods.dev/badge/skills/bx33661/oh-my-vul/omv-critic/github.svg)](https://agentmods.dev/skills/bx33661/oh-my-vul/omv-critic)
Your own site
<a href="https://agentmods.dev/skills/bx33661/oh-my-vul/omv-critic"><img src="https://agentmods.dev/badge/skills/bx33661/oh-my-vul/omv-critic/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 omv-critic

Your own site · 80×15
<a href="https://agentmods.dev/skills/bx33661/oh-my-vul/omv-critic"><img src="https://agentmods.dev/badge/skills/bx33661/oh-my-vul/omv-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 982 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.00083 $0.00982
Opus 5 $0.00042 $0.00491
Sonnet 5 $0.00017 $0.00196
Haiku 4.5 $0.00008 $0.00098

Measured 11d ago against content hash 93a33184b886, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

omv-critic 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 11d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check_output.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/omv-critic/SKILL.md · 91 lines

How it starts

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

omv-critic

Challenge the finding before report submission.

Invocation

/omv-critic <id>

Workflow

  1. Read .omv/findings/<id>.yaml using contracts/evidence.v1.yaml as the local schema reference.
  2. If present, read .omv/threatmaps/<id>.yaml using contracts/threat-map.v1.yaml as the local schema reference.
  3. If present, read .omv/verifications/<id>.yaml using contracts/verification.v1.yaml as the local schema reference.
  4. Run or inspect omv findings validate <id> and omv verification validate <id> when the sidecar exists.
  5. Evaluate argument quality separately from structural validation.
  6. Evaluate acceptance precedent (below) — evidence quality and acceptance odds are different axes.
  7. Output reject_risk: low|medium|high and a recommended researcher_goal.
  8. For medium or high risk, list 3-5 likely CNA or maintainer rejection reasons and concrete strengthening actions.

Review Focus

  • novelty and duplicate risk
  • acceptance precedent (see below)
  • affected version proof
  • source -> sink -> guard clarity
  • local observed result quality
  • CVSS and impact overclaiming
  • disclosure readiness

If reject_risk: high, do not recommend /omv-report yet.

Acceptance-Precedent Method

Ask three questions the machine gates cannot:

  1. Class precedent in this ecosystem: has this CNA/database accepted this vulnerability class for library packages before (e.g. code execution in a parser when input is attacker-controlled in realistic deployments)? No precedent means higher bar: the finding needs an airtight untrusted-input story, not just a reachable sink.
  2. Maintainer stance: does the project document the behavior as intended (opt-in features, "power user" escape hatches, README warnings)? By-design findings die at the maintainer even when technically real. Check README/docs/issues for the project's stated position.
  3. Public discussion: verify the dedup block covers the discussion sources (issues/PRs, commits, blogs — all six fields). An advisory-clean finding with an unsearched issue tracker is an unreviewed novelty claim: do not greenlight /omv-report until those searches are recorded. A public issue/PR disclosing the same bug caps reject_risk at high regardless of evidence quality.

Read the full file on GitHub · 91 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 91 lines · 83 tokens per session scan A 93a33184b886

Subscribe to this mod's changes

omv-critic is a skill published in the GitHub repository bx33661/oh-my-vul (4 stars, last pushed 22d ago), licensed MIT. It adds 83 tokens to every session and 982 once invoked, about $0.0004 per session on Opus 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-31.

CVECode reviewSecurityai-skillsclaude-skillsgithub-advisoryopen-source-securitysecurity-research
Related

Other skills, from other repositories

neo-code-review

Use this skill when the user asks to review or audit source code, a PR, diff, commit, or recent changes for bugs, security, performance, tests, compatibility, or maintainability, duplicated code or logic across files, or hard-coded values. Also use it after an AI agent finishes modifying code to inspect the current…

Benknightdark/neo-skills · 87 tokens

neo-pr

Use this skill when the user asks to create, draft, review, format, or generate a Pull Request (PR) title and description, specify target or source branches for a repository, or convert git branch diffs into concise, high-impact, non-AI-slop PR content.

Benknightdark/neo-skills · 60 tokens

neo-rust

Use this skill when writing, refactoring, debugging, or auditing Rust code. Trigger for .rs files, Cargo projects, ownership/borrowing/lifetime issues, Result/Option error handling, unnecessary clone/performance work, unsafe code review, or modern Rust architecture.

Benknightdark/neo-skills · 58 tokens

pr-walkthrough

Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.

aiskillstore/marketplace · 52 tokens

respond-to-pr-comments-in-blocklist

Interactively walk a user through PR review comments one at a time, collect a per-comment decision, then post agent-authored replies on GitHub and resolve the review threads once the user approves a preview. Use only when the user wants to reply to or resolve review threads on GitHub. Skip when the user only wants…

aiskillstore/marketplace · 98 tokens

review-loop

Iterative worker-reviewer cycle that spawns a critic subagent to score work 1-10 and provide actionable feedback, then revises until a quality gate is met. Use when implementing features, writing specs, reviewing existing code, or completing any task where quality matters more than speed. Trigger phrases: "use…

aiskillstore/marketplace · 89 tokens