skill-bx33661-oh-my-vul-omv-radar · by Install
$ agentstack add skill-bx33661-oh-my-vul-omv-radar ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bx33661-oh-my-vul-omv-radar) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
omv-radar
Maintain passive intelligence for watched packages and vulnerability classes.
Invocation
/omv-radar refresh [--dry-run]
/omv-radar briefWorkflow
- Read
.omv/radar/watchlist.yaml. - For refresh, prefer the CLI:
omv radar refresh --dry-runfor fixture-backed offline validation.omv radar refreshfor local event append.
- For summaries, run
omv radar brief. - Group output by ecosystem, package, and signal type: advisory, release, suspected fix, or watchlist snapshot.
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bx33661
- Source: bx33661/oh-my-vul
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.