Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vercel-labs avatar

Deepsec

  • 159 installs
  • 6.4k repo stars
  • Updated July 26, 2026
  • vercel-labs/deepsec

deepsec skill for running AI vulnerability scans, configuring projects, and authoring matchers and plugins.

About

Meta skill for deepsec, an AI-powered vulnerability scanner activated when deepsec ships in node_modules or from a vercel-labs/deepsec clone. Points to dist/docs for getting-started, configuration, plugins, writing-matchers, models, vercel-setup, architecture, data-layout, and faq. References samples/webapp as a complete config with inline plugin, custom matchers, INFO.md, and config.json. Instructs reading docs before answering because CLI flags, defaults, and plugin contract fields change. Maps common questions to specific doc files rather than paraphrasing from training data.

  • AI-powered vulnerability scanner with docs in node_modules/deepsec/dist/docs
  • Configuration reference in configuration.md and samples/webapp example
  • Plugin slots: matchers, notifiers, ownership, people, executor
  • writing-matchers.md for growing matcher set with a coding agent
  • vercel-setup.md for AI Gateway and Vercel Sandbox token setup

Deepsec by the numbers

  • 159 all-time installs (skills.sh)
  • +9 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #858 of 2,209 Security skills by installs in the Skillselion catalog
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

deepsec capabilities & compatibility

Capabilities
run deepsec scan · configure deepsec project · author matchers · write plugins · read deepsec docs
Works with
vercel
Use cases
security audit · testing
Runs
Runs locally
npx skills add https://github.com/vercel-labs/deepsec --skill deepsec

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs159
repo stars6.4k
Last updatedJuly 26, 2026
Repositoryvercel-labs/deepsec

How do I run, configure, or extend deepsec vulnerability scans in my project?

Run, configure, and extend deepsec AI-powered vulnerability scans including matchers, plugins, and project configuration in node_modules or clone setups.

Who is it for?

Developers using deepsec locally or from vercel-labs/deepsec clone for security scanning.

Skip if: Generic SAST tools unrelated to deepsec or production incident response.

When should I use this skill?

User asks how to scan, configure, or extend deepsec in a project with deepsec installed.

What you get

Scan executed or config/matcher/plugin authored following current deepsec documentation.

Files

SKILL.mdMarkdownGitHub ↗

deepsec

deepsec is an AI-powered vulnerability scanner. This skill activates when deepsec ships inside node_modules/ — typically because the user ran npx deepsec … (which caches the package locally). In the more common dedicated-git setup the user works inside a clone of vercel-labs/deepsec and the same docs sit at docs/ from the repo root — read those instead when this skill fires from outside a node_modules.

When the user asks how to use, configure, or extend deepsec, read the relevant doc before answering — the docs are the source of truth, not your training data.

Where the docs are

node_modules/deepsec/dist/docs/ (or <deepsec-clone>/docs/):

  • getting-started.md — first-scan walkthrough
  • configuration.md — full deepsec.config.ts reference
  • plugins.md — plugin slots (matchers, notifiers, ownership, people, executor)
  • writing-matchers.md — how to grow the matcher set with a coding agent
  • models.md — model selection, defaults, refusals, future models
  • vercel-setup.md — getting AI Gateway and Vercel Sandbox keys / tokens
  • architecture.md — pipeline internals
  • data-layout.mddata/ schemas (FileRecord, RunMeta, …)
  • faq.md — cost, model choice, sandbox mode, FP rate

Worked example

node_modules/deepsec/dist/samples/webapp/ (or <deepsec-clone>/samples/webapp/) is a complete reference setup — deepsec.config.ts with an inline plugin, two custom matchers under matchers/, an INFO.md for AI prompt context, and a per-project config.json. When the user asks "what should my config look like?", read this directory.

How to answer common questions

  • "How do I run a scan?"getting-started.md.
  • "What goes in `deepsec.config.ts`?"configuration.md + samples/webapp/deepsec.config.ts.
  • "How do I add a matcher?"writing-matchers.md + samples/webapp/matchers/*.ts.
  • "How do I write a plugin?"plugins.md + samples/webapp/deepsec.config.ts (inline plugin pattern).
  • "What does deepsec actually do?"architecture.md.
  • "What's in `data/<id>/files/foo.json`?"data-layout.md.
  • "Which model / agent should I use?"models.md.
  • "How do I get an AI Gateway / Sandbox token?"vercel-setup.md.

Read the doc before paraphrasing. The CLI flag set, defaults, and plugin-contract field names change — quote the doc, don't recall.

Related skills

FAQ

Where are deepsec docs located?

node_modules/deepsec/dist/docs/ or docs/ from a deepsec clone; read before answering.

What is the reference project layout?

samples/webapp has deepsec.config.ts, matchers/, INFO.md, and config.json as a complete example.

How do I add a custom matcher?

See writing-matchers.md and samples/webapp/matchers/*.ts for patterns.

Securityauditappsec

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.