Synthesizes trust boundaries, attack surfaces, and attacker profiles into a living threat model. Use as Stage B of the Knowledge Base generation process, reading architecture and entity definitions from the KB. Don't use for analyzing source code or extracting raw learnings from JSONL files.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmantis-threat-modelExecute the skills CLI command in your project's root directory to begin installation:
Fetches mantis-threat-model 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-threat-model. Access via /mantis-threat-model 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-threat-model |
| description | >- Synthesizes trust boundaries, attack surfaces, and attacker profiles into a living threat model. Use as Stage B of the Knowledge Base generation process, reading architecture and entity definitions from the KB. Don't use for analyzing source code or extracting raw learnings from JSONL files. |
Security Architect. Synthesizes trust boundaries, attack surfaces, and attacker
profiles into THREAT_MODEL.md based exclusively on the entities and
architecture defined in the Knowledge Base (KB).
/mantis-threat-modelworkspace/.mantis_state.json (to track current loop pass).workspace/kb/architecture.md.workspace/kb/entities/*.md.workspace/kb/THREAT_MODEL.md.workspace/kb/THREAT_MODEL.md in-place.Maintain a high-level Threat Model that explicitly defines who the attackers are and where they can interact with the system, relying on the pre-processed entities in the KB.
Execute the threat modeling process as follows:
Read the Synthesized KB:
workspace/kb/architecture.md to understand the system's data
flows and high-level design.workspace/kb/entities/ to understand the
individual components and any historical constraints or vulnerability
patterns mapped to them by the /mantis-architecture stage.Analyze Trust Boundaries:
Synthesize the Threat Model:
workspace/kb/THREAT_MODEL.md (overwriting the old one).Include the following sections to ensure downstream planning agents have sufficient context:
architecture.md.Intent: SAMPLE_OR_TEST_ONLY
or Intent: PRODUCTION).[Auth Module](entities/auth_module.md)).CRITICAL: 24/7 immediate operational impact if disrupted.STANDARD: Important operations; short downtime is tolerable.LOW_CRITICALITY: Non-blocking utilities; disruption is a mild
annoyance.Save your final output directly to workspace/kb/THREAT_MODEL.md. 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.
We added mantis-threat-model from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: mantis-threat-model is focused, and the summary matches what you get after install.
mantis-threat-model fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend mantis-threat-model for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in mantis-threat-model — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added mantis-threat-model from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: mantis-threat-model is the kind of skill you can hand to a new teammate without a long onboarding doc.
mantis-threat-model is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in mantis-threat-model — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: mantis-threat-model is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 71