mantis-plan

Generate targeted security review plans from codebase structure and threat models.

731|84|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/google/mantis --skill mantis-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mantis-plan
Source: https://github.com/google/mantis/tree/main/mantis-plan
Command: npx skills add https://github.com/google/mantis --skill mantis-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining comprehensive and efficient security review coverage in complex, evolving codebases by automating the generation of targeted, risk-aware audit plans.

Core Features & Use Cases

  • Adaptive Planning: Automatically crawls codebases to generate a structured review roadmap (plan.json) based on threat models and historical findings.
  • Incremental Efficiency: Uses VCS diffs and dependency analysis to focus reviews on changed code and its consumers, preventing redundant work.
  • Use Case: When starting a new security campaign, use this skill to map the attack surface and generate a prioritized list of files to audit, ensuring that recent changes and high-risk interfaces are covered first.

Quick Start

Execute the mantis-plan skill to analyze the current directory and generate a defensive security review roadmap in the workspace folder.

Frequently Asked Questions about mantis-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a security audit plan for a complex codebase?

To generate a security audit plan, this skill analyzes codebase structure, threat models, and historical vulnerability data to formulate a targeted defensive review roadmap. It automatically crawls your directories to produce a structured plan.json file.

How does incremental code review work for vulnerability management?

Incremental code review works by utilizing VCS-aware diffing and dependency-graph analysis to focus security reviews exclusively on changed components and their consumers. This approach prevents redundant work and maintains idempotency through state-based tracking.

Can I use threat modeling to prioritize source code and firmware security audits?

Yes, you can use threat modeling to prioritize security audits across diverse targets including source code, binaries, and firmware. The skill maps boundaries and prioritizes investigation paths based on the provided threat models and historical findings.

What is the best way to map an attack surface before starting a security campaign?

The best way to map an attack surface is to execute an automated analysis of your current directory to map boundaries and generate a prioritized list of high-risk files. This ensures recent changes and critical interfaces are covered first.

Does this automated security review tool maintain state between audits?

Yes, this automated security review tool maintains state between audits by utilizing state-based tracking and idempotency. This ensures exhaustive coverage of changed components without duplicating previous review efforts.

Why focus security reviews on VCS diffs and dependency graphs?

Focusing security reviews on VCS diffs and dependency graphs ensures exhaustive coverage of changed code and its downstream consumers while maximizing efficiency. This prevents redundant work by targeting only the modified attack surface.