Generate security-focused directory summaries via bottom-up repository traversal.
npx skills add https://github.com/google/mantis --skill mantis-summarize
Please help me install this Agent Skill. Skill: mantis-summarize Source: https://github.com/google/mantis/tree/main/mantis-summarize Command: npx skills add https://github.com/google/mantis --skill mantis-summarize
This skill addresses the challenge of high token overhead during security reviews by generating concise, security-focused summaries of directory contents, allowing agents to navigate large codebases efficiently.
Run the mantis-summarize command to generate security-focused summaries for all directories in the current repository.
High-intent search queries and answers about installing and using this skill.
Security-focused codebase mapping solves high token overhead by generating concise summaries of directory contents. It performs a bottom-up traversal to aggregate component, API, and vulnerability data, allowing agents to navigate large repositories efficiently during security analysis.
To generate security summaries for repository directory trees, run an automated command that recursively creates security-focused summary files. It operates by performing a bottom-up traversal of the repository tree to aggregate component, API, and vulnerability data into deterministic, actionable codebase maps.
Yes, local filesystem access is required to generate codebase maps for threat modeling. The process requires local filesystem access and historical learning logs to produce deterministic, actionable repository maps and security-focused directory summaries.
Yes, automated repository mapping optimizes context window usage for security analysis by abstracting low-level details into concise directory summaries. It reduces token usage while preserving critical security information like trust boundaries and sensitive operations for downstream threat modeling.
Limitations of automated codebase summaries for security audits include the requirement for local filesystem access and historical learning logs. Additionally, abstracting low-level details to optimize token usage may omit granular implementation logic needed for highly specific vulnerability investigations.
St33f3nTraverse a codebase and generate a YAML summary of relevant code snippets.
brenordvAudit software systems for security vulnerabilities and regulatory compliance.
chicongstAudit trust boundaries, data flows, and secrets handling to produce a structured security review report.
ils15Visualize directory trees and module relationships in codebases.
