Pre-processes the repository by generating security-focused summaries (mantis-summary.md) for each directory to make planning and research more efficient. Use when starting a review campaign to map the codebase before threat modeling and planning. Don't use for executing code reviews, writing test scripts, or patching code.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmantis-summarizeExecute the skills CLI command in your project's root directory to begin installation:
Fetches mantis-summarize from google/mantis and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate mantis-summarize. Access via /mantis-summarize in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
307
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
307
stars
| name | mantis-summarize |
| description | >- Pre-processes the repository by generating security-focused summaries (mantis-summary.md) for each directory to make planning and research more efficient. Use when starting a review campaign to map the codebase before threat modeling and planning. Don't use for executing code reviews, writing test scripts, or patching code. |
Repository Mapper. Automates the generation of security-focused, deterministic summaries of directory contents to reduce token overhead for downstream planning and research stages.
/mantis-summarizemantis-summary.md) for each directory to make planning and
research more efficient.workspace/.mantis_state.json (to track current loop pass).node_modules,
vendor, .git, build outputs, and tests/).mantis-summary.md files from
subdirectories).workspace/historical_learnings.jsonl (optional, to enrich summaries).mantis-summary.md file in each directory containing source code.mantis-summary.md files in-place
with updated rollups.Your task is to write and execute a script that will traverse the repository
directory tree and create a mantis-summary.md file in each directory
containing source code.
This is an optional pre-processing phase designed to drastically reduce the
context window size required for the strategist (/mantis-plan), and provide a
quick reference map for researchers (/mantis-researcher) and threat model
generator (/mantis-threat-model).
Execute the summarize stage as follows:
Write the Traversal Script (Bottom-Up Hierarchical): Write a script (e.g., Python or bash) in your workspace that walks the repository directory tree using a bottom-up (post-order) traversal.
node_modules, vendor, .git, build outputs, and tests/.mantis-summary.md files of
its immediate subdirectories. Do not pass the raw source files of
subdirectories to the parent.Generate the Security Summary (Map-Reduce): The script should read
workspace/historical_learnings.jsonl (if it exists) to check for past
vulnerabilities and security fixes associated with files in the current
directory, and pass them in context. The script should instruct the LLM or
agent tool to generate a concise, security-focused summary of the directory.
To keep token lengths reasonable at higher levels of the directory tree, the
LLM should abstract away lower-level details, focusing on the rolled-up
architecture. The prompt used by your script should ask for:
workspace/historical_learnings.jsonl? Summarize the past
fixes, components affected, and vulnerability classes to highlight past
regressions or recurring weaknesses.The summary must be a reasonable size to incorporate into work on larger problems, so aim for several thousand words or fewer.
Output to mantis-summary.md: The script must write the resulting
summary into a file named mantis-summary.md inside the corresponding
directory. Overwrite it if it already exists.
Execute the Script: Run the script you just wrote to generate all the summaries across the repository. Wait for it to finish successfully.
When complete, notify the user.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
mantis-summarize fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for mantis-summarize matched our evaluation — installs cleanly and behaves as described in the markdown.
mantis-summarize reduced setup friction for our internal harness; good balance of opinion and flexibility.
mantis-summarize has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in mantis-summarize — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added mantis-summarize from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend mantis-summarize for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: mantis-summarize is focused, and the summary matches what you get after install.
I recommend mantis-summarize for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: mantis-summarize is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 41