mantis-critic

Assess production viability of security findings by verifying code reachability in optimized release builds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill filters out false positives and debug-only findings by verifying if security vulnerabilities are actually triggerable in optimized, production-ready release builds.

Core Features & Use Cases

  • Production Viability Assessment: Distinguishes between theoretical flaws and actionable bugs by checking for debug-only code paths and assertion traps.
  • Snapshot-Aware Verification: Uses immutable code snapshots to ensure findings are evaluated against the exact state of the codebase where they were discovered.
  • Use Case: After an automated scanner identifies a potential memory safety issue, use this skill to confirm if the code path is reachable in a production binary where assertions are disabled.

Quick Start

Run the mantis-critic skill to evaluate the production viability of all findings currently stored in the workspace directory.

Frequently Asked Questions about mantis-critic

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

FAQPage Schema
How do I filter out debug-only security vulnerabilities in production builds?

Filter debug-only security vulnerabilities by assessing code reachability within optimized release configurations, ensuring identified flaws are triggerable when assertions are disabled. This confirms production viability and removes theoretical debug-only traps.

What is production viability assessment for security findings?

Production viability assessment distinguishes actionable bugs from theoretical flaws by checking for debug-only code paths and assertion traps, verifying that vulnerabilities are actually reachable in production-ready release builds.

How do I validate if a memory safety issue is reachable in a release binary?

Validate memory safety reachability by operating on an immutable codebase snapshot to perform drift analysis, confirming whether the vulnerable code path survives in an optimized build with assertions disabled. This filters false positives.

Do I need Mantis state management to verify code reachability?

Yes, verifying code reachability requires integration with Mantis state management and workspace findings to perform accurate drift analysis and threat model validation against pinned codebase snapshots. This ensures precise production viability assessment.

How does snapshot-aware verification improve static analysis results?

Snapshot-aware verification improves static analysis results by using immutable code snapshots to ensure findings are evaluated against the exact codebase state where discovered, preventing drift-related false positives and inaccurate threat modeling.