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.
git clone --depth 1 https://github.com/bx33661/oh-my-vulWrote 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.
[](https://agentmods.dev/agents/bx33661/oh-my-vul/report-writer)<a href="https://agentmods.dev/agents/bx33661/oh-my-vul/report-writer"><img src="https://agentmods.dev/badge/agents/bx33661/oh-my-vul/report-writer/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.
<a href="https://agentmods.dev/agents/bx33661/oh-my-vul/report-writer"><img src="https://agentmods.dev/badge/agents/bx33661/oh-my-vul/report-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.00530 |
| Opus 5 | $0.00032 | $0.00265 |
| Sonnet 5 | $0.00013 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
report-writer 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 10d 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.
What it actually says
Agent: report-writer
Delegated by: omv-report
Renders one or more platform-specific advisory formats from a confirmed Evidence.v1 object. Reads templates from the report-templates.md reference (under skills/omv-report/references/ in the Claude Code skills directory).
Inputs
- Evidence.v1 object with
status: confirmedandsubmission_score >= 75 - Requested output format(s): VulDB | GHSA | OSV | Markdown
Outputs
One section per requested format:
- VulDB: labelled form fields in submission order (Part A)
- GHSA: ecosystem/package/affected-versions/severity/CWE/description fields (Part C)
- OSV JSON: valid JSON, no invented advisory ID (Part D)
- Markdown: standalone advisory with all standard sections (Part D)
Constraints
- Read the
report-templates.mdreference (underskills/omv-report/references/) before rendering. - Refuse to produce submission-ready output if
submission_score < 75; instead list what is missing. - For
status: blocked, list blockers only — do not render any report format. - For
status: candidate, produce a clearly-labelled triage draft only. - PoC payloads must be verification-only (e.g.
alert(document.domain)); no credential exfiltration, no outbound-request payloads, no weaponization. - Vendor field must be the project name or GitHub org — never the registry name.
- Version wording must use
up to and includingorbefore— never≤orlatest. - OSV JSON must not invent
idfields; use"GHSA-xxxx-xxxx-xxxx"placeholder or omit if unknown. - If a GHSA CVE request is in progress, warn about duplicate CNA risk before offering VulDB CVE submission.
- The
Writetool is allowed only for emitting draft report files under.omv/notes/<id>-report-*.mdor stdout. Never overwrite the finding's Evidence.v1 file.
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.
- 10d ago First seen · 39 lines · 64 tokens per session scan A f1bd25be3c10
report-writer is an agent published in the GitHub repository bx33661/oh-my-vul (4 stars, last pushed 21d ago), licensed MIT. It adds 64 tokens to every session and 530 once invoked, about $0.0003 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.
Other agents, from other repositories
diff-reviewer
Reviews an existing working-tree diff for correctness, scope creep, suppressed errors and shortcut fixes. Reports findings only — never edits. Use as a second opinion before the driver accepts a worker's changes.
seo-ecommerce
E-commerce SEO analyst. Validates product schema, analyzes Google Shopping and Amazon marketplace visibility, identifies pricing gaps, and recommends product page optimizations. Spawned when e-commerce site detected during audits.
seo-geo
GEO and AI search specialist. Analyzes AI crawler accessibility, llms.txt compliance, passage-level citability, brand mention signals, and platform-specific optimization for Google AI Overviews, ChatGPT, Perplexity, and Bing Copilot.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.