securevibes-scanner
Run AI-powered application security scans on codebases. Use when asked to scan code for security vulnerabilities, generate threat models, review code for security issues, run incremental security scans, or set up continuous security monitoring via cron. Supports full scans (one-shot) and incremental scans (cron-driven, only new commits).
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/anshumanbh/securevibes-scannerSecureVibes Scanner
AI-native security platform that detects vulnerabilities using Claude AI. Multi-subagent pipeline: assessment → threat modeling → code review → report generation → optional DAST. Supports incremental scanning for continuous monitoring.
Prerequisites
- Install the CLI:
pipx install securevibes(preferred) oruv tool install securevibes. Avoidpip install— it can create stale shims if you have multiple Python environments. - Authenticate with Anthropic (one of):
- Max/Pro subscription (recommended): If you're authenticated via Claude Code or Claude CLI OAuth, no API key is needed. The Claude Agent SDK picks up your OAuth session automatically. When running inside OpenClaw, leave
ANTHROPIC_API_KEYunset or blank — the SDK handles auth. - API key:
export ANTHROPIC_API_KEY=your-key-here(from console.anthropic.com)
- Max/Pro subscription (recommended): If you're authenticated via Claude Code or Claude CLI OAuth, no API key is needed. The Claude Agent SDK picks up your OAuth session automatically. When running inside OpenClaw, leave
Security Notes
- Always use the
scripts/scan.shwrapper for full scans — it validates paths and rejects shell metacharacters before invokingsecurevibes. - Never interpolate unsanitized user input into shell commands.
- The wrapper uses
realpathto resolve paths safely and rejects any path containing;,|,&,$, backticks, or other metacharacters. - Scan targets must be local directories. Clone remote repos to a known safe location first, then pass the resolved path to the wrapper.
- DAST scans make network requests to the
--target-urlyou provide. Only use against apps you own or have permission to test.
Execution Model
Full scans take 10-30 minutes across 4 phases. Run them as background jobs (cron or subagent), not inline.
Incremental scans take 2-10 minutes — they only scan commits since the last run.
Full Scan (One-Shot)
Running a Scan
- Clone the target repo to a local directory
- Run the wrapper script:
bash scripts/scan.sh /path/to/repo --force --debug - Results appear in
/path/to/repo/.securevibes/
Background Execution (Recommended)
For OpenClaw users, schedule scans as cron jobs:
- Use
sessionTarget: "isolated"withpayload.kind: "agentTurn" - Set
payload.timeoutSeconds: 2700(45 minutes) to allow all phases to complete - Use
delivery.mode: "announce"to get notified when done
The agentTurn message should instruct the subagent to:
cdinto the repo andgit pullfor latest code- Clean previous
.securevibes/artifacts - Run
securevibes scan . --forcevia the wrapper script - Read and summarize the results from
.securevibes/scan_report.md
Incremental Scan (Continuous Monitoring)
The incremental scanner (ops/incremental_scan.py) tracks the last-scanned commit and only scans new commits. Designed for cron-driven continuous security monitoring.
How It Works
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-anshumanbh-securevibes-scanner": {
"enabled": true,
"auto_update": true
}
}
}