A skill for operating Vercel's deepsec, an agent-assisted scanner that looks through code repositories for security vulnerabilities. It also handles scan results, rechecking, custom matchers, exports, and pull-request checks.

Use it to set up deepsec, scan a repository, triage or revalidate findings, create project-specific matching rules, export results, or gate pull requests on security checks.

It helps find and review security problems in code and can make changed-code checks part of continuous integration.

oma-deepsec — Skill for Claude Code and Codex by first-fluke

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 first-fluke/fullstack-starter --skill oma-deepsec

Clone the repo

git clone --depth 1 https://github.com/first-fluke/fullstack-starter

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-deepsec/github.svg)](https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-deepsec)

Your own site

<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-deepsec"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-deepsec/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-deepsec"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-deepsec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,928 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.04928
Opus 5.5	$0.00014	$0.01971
Sonnet 5.5	$0.00007	$0.00986
Haiku 4.5	$0.00003	$0.00493

Measured 14d ago against content hash 6773a3a2cb80, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

oma-deepsec scanned grade C with 1 finding 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 14d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

oma-deepsec — 97% identical, 69 lines differ

.agents/skills/oma-deepsec/SKILL.md · 217 lines

How it starts

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

Deepsec: Agent-Powered Vulnerability Scanner Driver

Scheduling

Goal

Operate Vercel's deepsec security scanner inside a target repository safely and cost-consciously: bootstrap the .deepsec/ workspace, write a tight INFO.md, run the right scan/process/triage/revalidate/export sequence, gate PRs in CI via process --diff, and grow project-specific matchers, surfacing real, revalidated findings without runaway spend.

Intent signature

User mentions deepsec, "deep security scan", bunx deepsec, pnpm deepsec, npx deepsec.
User asks an agent to scan a repository for vulnerabilities, security issues, or CVEs and the project has (or should have) a .deepsec/ directory.
User asks how to add a deepsec PR / CI security gate, or about process --diff, --diff-staged, --diff-working, --files-from, --comment-out.
User mentions deepsec artefacts: INFO.md, SETUP.md, data/<id>/files/, FileRecord, RunMeta, revalidation, triage, custom matchers, MatcherPlugin, noiseTier, priorityPaths.
User asks about deepsec configuration: deepsec.config.ts, defaultAgent, AI_GATEWAY_API_KEY, VERCEL_OIDC_TOKEN, AI Gateway, Vercel Sandbox, --agent codex, --agent claude.
User asks how to lower deepsec cost, cut false-positive rate, or interpret severity / triage / revalidation verdicts.

When to use

First-time deepsec install in a repo (init, INFO.md write, first calibration scan).
Running a full or scoped scan and processing findings.
Setting up a per-PR CI gate with process --diff and --comment-out.
Writing a project-specific matcher to cover entry points the default set misses.
Triaging a backlog of findings (severity bucketing, FP cuts via revalidate, exporting to issue tracker).
Diagnosing deepsec failures: missing credentials, AI Gateway quota stops, refusals, sandbox auth.

When NOT to use

Generic OWASP / lint-style review without deepsec → use oma-qa.
Generic CVE / dependency advisories → use oma-qa or oma-search.
Architecting a brand-new SAST pipeline that is not deepsec → use oma-architecture.
Writing or auditing application code itself → route to oma-backend / oma-frontend / oma-mobile.
Cloud / IAM / Terraform hardening → use oma-tf-infra (deepsec only scans the IaC; remediation lives there).
Pure reasoning about a finding's fix in product code → use oma-debug once deepsec has produced the finding.

Read the full file on GitHub · 217 lines

Files

What ships with it

7 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.

14d ago Changed · +3 lines 6773a3a2cb80
1mo ago Changed · -38 lines · -164 tokens per session 93cac8998e7b
1mo ago First seen · 252 lines · 199 tokens per session scan C 82f9a9467318

Subscribe to this mod's changes

oma-deepsec is a skill published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 4,928 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

CI and CD DevOps and cloud Security fastapi flutter gcp mise monorepo nextjs

android-tooling

Configure Android static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates. Use for Android-specific lint and quality tooling; defer generic Java Checkstyle, SonarQube, and standalone CI configuration.

HoangNguyen0403/agent-skills-standard · 51 tokens

billing-stripe

Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.

vstorm-co/full-stack-ai-agent-template · 56 tokens

oma-deepsec