/vibe_hacking

Performing secure code review with LLMs (and vibe coding IDEs)

Apache License 2.0Apache-2.0

Vibe Hacking

This repo contains content for performing secure code review with LLMs (/vibe coding IDEs).

Currently the contents are from Scott Behren and Clint Gibler's webinar on using Roo Code for performing secure code reviews, but new content may be added in the future.

Features

The roomodes file in this repo contains 5 custom roles:

  1. Security Orchestrator - Orchestrates the overall workflow and coordinates the following agents.
  2. Threat Modeler - Creates a threat model for a code base, documenting the project's architecture, technologies used, attack surface, trust boundaries, and more.
  3. Security Scanner - Uses automated tools (Semgrep) and LLM-driven code review to find vulnerabilities in a code base.
  4. Security Tracer - Given a set of findings, it uses code search to determine if the findings are likely exploitable- could an attacker provide the relevant input? Does sanization occur along the exploitation path? etc.
  5. Security Reporter - Given a set of findings that have been traced, write a report on the security assessment, include an executive summary, the scope, and a detailed write-up for each finding.

Getting Set Up

  1. Install VS Code and the Roo Code extension.
  2. Install dependencies.
    1. Install Semgrep for the code scanning part of the workflow.
      • Note: If you want inter-file analysis and 1000's of additional rules, check out Semgrep Pro.
      • The provided .roomodes will work regardless though.
    2. If you want to take advantage of the Security Tracer Roo mode, which triages findings to determine if they are real issues ("True Positives"), set up the vector database Qdrant, which you can get a free hosted account for or run locally in Docker.
  3. Configure Roo Code.
    1. In the Roo Code extension within VS Code, choose your LLM provider of choice and provide your API keys.
      • In the webinar, we used Anthropic's Claude 4.0 Sonnet.
    2. Configure codebase indexing using Qdrant.
    3. Copy the roomodes file in this folder into the project root of the repo you're reviewing (rename it to .roomodes), or globally in ~/.roo/. See the Roo docs for more info.

Usage

Within the Roo Code extension in VS Code, when you've cloned down a repo you want to analyze, type into Roo Code:

Perform a security assessment of path/to/repo_target

Notes

While this repo currently contains the security analysis prompts in a .roomodes file, those same prompts could likely be used almost verbatim with other coding agents, such as Claude Code's Slash commands or Subagents.

See also the Google Slides accompanying the webinar.

Other great resources:

Contributing

If you've written additional prompts or Roo modes, or have improved on the ones in the repo, feel free to open a PR, we'd love to see what you've been cooking!