Testing Handbook Skills
Security scan passedTrail of Bits' skills for fuzzing and crypto testing, from its Testing Handbook: libFuzzer, AFL++, cargo-fuzz, Atheris, OSS-Fuzz and more.

Scans AI-written code for the 21 most common vulnerability types, explains each one in plain words, and shows the fixed code.
Pack · 1 skillby tanviet12· SecurityUnclaimed · Yours? Claim it
4 images
About
A community Agent Skill by tanviet12 for checking AI-written code for security holes. It reads your code, traces data from user input to dangerous calls rather than matching strings, and reports each issue with why it's dangerous, how an attacker would use it, the current code and the fix. It's written for people who aren't security experts. What it catches - 21 common vulnerability types, including secrets in source code, SQL injection, broken access control, JWTs accepted without signature checks and wide-open CORS - Deep coverage of Go, PHP, TypeScript and JavaScript, Python and .NET, including Express, NestJS, Next.js, React, Django, FastAPI, Laravel and ASP.NET Core How it works - Scan the whole repo, only uncommitted changes, one commit, one pull request or the last few days of commits, or a plain folder without git. - Large repos are split across several agents in parallel and the results merged. - Reports are saved as files in vbsec-reports/, in English or Vietnamese, with a JSON summary for CI. - Install it as a skill for your coding agent, following the README's install steps. Good to know - The repo ships sample apps with planted bugs that it tests itself against. - It finds and explains issues; you decide which fixes to apply. - MIT licensed.
Skills people install alongside vbsec.
Once it’s added
“Scan this repo for security vulnerabilities”
“Check my uncommitted changes for security issues before I push”
“Scan this pull request for vulnerabilities”
“Review the last 7 days of commits for security problems”
“Scan the AI-generated code in this folder”
Before you add it
Reads only
Your source code, commits and pull requests
Makes changes · your agent can ask first
Security reports in a vbsec-reports folder, with a JSON summary
Pack · 1 skill, each with its own page
From people who use it
Step by step
Nothing new reaches your agent until a person has looked at it.
Scanned on every change, and again when our rules improve.
Runs on your machine.
Runs on your machine.
Runs on your machine.
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.copilot/skills/vbs-scan-security
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.cursor/skills/vbs-scan-security
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.claude/skills/vbs-scan-security
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.agents/skills/vbs-scan-security
Runs on your machine.
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.gemini/skills/vbs-scan-security
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security .agents/skills/vbs-scan-security
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.openclaw/skills/vbs-scan-security
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.config/opencode/skills/vbs-scan-security
Runs on your machine.
npx -y degit tanviet12/vbsec/skills/antigravity/vbs-scan-security ~/.hermes/skills/vbs-scan-security
Scanned and passed · checked 47 min ago
No reviews yet. Used vbsec? Say how it went.
Write a reviewNobody has shared how they use vbsec yet.
Security scan
Passed
Safe to install in every agent it supports. Runs in your agent, as instructions.
Skills people install alongside vbsec.
Trail of Bits' skills for fuzzing and crypto testing, from its Testing Handbook: libFuzzer, AFL++, cargo-fuzz, Atheris, OSS-Fuzz and more.
Lets your agent find vulnerabilities in your code, prove they're real against your running app, and fix them: SCA, secrets, SAST and DAST.
Has your agent diff two Windows builds with WinDiff and explain what changed in syscalls, symbols and mitigations, and why it matters.