oma-deepsec

Drives Vercel's deepsec agent-powered vulnerability scanner through setup, scanning, triage, and CI gating.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/javiruu/viru-air --skill oma-deepsec-javiruu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oma-deepsec
Source: https://github.com/javiruu/viru-air/tree/main/.agents/skills/oma-deepsec
Command: npx skills add https://github.com/javiruu/viru-air --skill oma-deepsec-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running an AI-driven security scanner like Vercel's deepsec involves expensive LLM calls, complex credential setup, and multi-stage workflows (scan, process, triage, revalidate, export). This Skill orchestrates the entire deepsec lifecycle cost-consciously, preventing runaway spend and misconfigured CI security gates. ## Core Features & Use Cases - Workspace Bootstrap: Installs the .deepsec/ workspace, configures AI credentials (AI Gateway, OIDC, direct provider keys), and writes a project-specific INFO.md that improves finding precision. - Cost-Aware Scanning: Enforces calibration passes (--limit 50 --concurrency 5) with cost extrapolation before any full process run, and resumes safely after quota or network interruptions. - PR Security Gating: Scaffolds a two-job CI workflow using process --diff with --comment-out, keeping PR-controlled code in a no-write job. - Custom Matchers & Triage: Authors project-specific matchers in .deepsec/matchers/, runs triage and revalidate to cut false positives, and exports findings to markdown or JSON. - Use Case: A team wants to add an AI security review to every pull request. This Skill sets up deepsec, calibrates cost on a sample of files, wires the two-job GitHub Actions workflow, and surfaces only revalidated HIGH+ findings as PR comments. ## Quick Start Ask the agent to set up deepsec in this repository, run a calibration scan on 50 files, and report the estimated cost of a full scan before proceeding.

Frequently Asked Questions about oma-deepsec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up deepsec to scan my repository for vulnerabilities?▼

Run bunx deepsec init from your repo root, then install dependencies inside .deepsec/ and add an AI credential such as AI_GATEWAY_API_KEY to .env.local. Next, write a project-specific INFO.md (50-100 lines) and run a calibration pass with process --limit 50 --concurrency 5 before any full scan.

How do I add a deepsec security gate to pull requests in CI?▼

Use bunx deepsec process --diff origin/<base> --comment-out comment.md, which exits 1 only on net-new findings. The recommended pattern splits CI into two jobs: an analyze job with no write permissions that runs PR code, and a comment job with pull-requests: write that only posts the sanitized markdown artifact.

How much does a deepsec scan cost?▼

With the Claude Opus backend, roughly 100 files cost $25-60, 500 files $130-300, and 2,000 files $500-1,200, with 2-3x swing based on complexity. The Codex backend is cheaper. Always run a --limit 50 calibration pass first and extrapolate before launching a full process run.

What credentials does deepsec support for AI access?▼

Deepsec accepts an AI_GATEWAY_API_KEY (covering both Claude and Codex through Vercel AI Gateway), a VERCEL_OIDC_TOKEN, direct ANTHROPIC_AUTH_TOKEN or OPENAI_API_KEY, or a logged-in claude/codex CLI subscription. Subscriptions generally lack headroom for full scans, so the gateway is recommended.

How do I reduce false positives in deepsec findings?▼

Run bunx deepsec revalidate --min-severity HIGH, which re-reads code and git history to emit true-positive/false-positive verdicts and typically cuts FP rate by over 50%. Tightening INFO.md with your auth shape, threat model, and known FP sources further improves precision.

When should I not use deepsec for security review?▼

Deepsec is not the right fit for generic OWASP or lint-style review, dependency CVE advisories, or cloud/IAM hardening beyond scanning IaC. It also should not run an unbounded process on a large unmeasured repo, since costs can reach thousands of dollars without calibration.