Skip to content
Agentmart
Submit a tool

threat-modeling

Skill by cellrishi-code

IndexedMIT★ 6
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/cellrishi-code-threat-modeling

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

The publisher has not written a description yet.

Use cases: security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/threat-modeling

What's inside

Skill name
threat-modeling
Description
None
License
MIT
Instructions
34 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • description: missing

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Lightweight Threat Modeling

## Purpose
Help teams identify security risks early by systematically examining assets, trust boundaries, threats, and mitigations.

## When to use
Use during feature planning, architecture reviews, major dependency changes, or before exposing a new service or API.

## Instructions
1. Define the system boundary, intended use, deployment context, and explicit exclusions.
2. List important assets, such as credentials, personal data, business records, and privileged operations.
3. Draw or describe components, data flows, entry points, external services, and trust boundaries.
4. For each flow, ask who can send input, what is trusted, what authorization is enforced, and what happens on failure.
5. Consider relevant threat categories: spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege.
6. Rank each threat using likelihood, impact, assumptions, and existing controls. Do not imply numeric precision without a defined scoring method.
7. Recommend mitigations that map directly to threats and identify an owner or verification test where possible.
8. Revisit the model when system boundaries, data sensitivity, or trust assumptions change.

## Inputs
- System purpose and architecture
- Data-flow description or diagram
- Assets and trust boundaries
- Deployment assumptions and existing controls

## Outputs
A concise threat register containing the threat, affected asset or flow, assumptions, impact, existing controls, recommended mitigation, and validation approach.

## Example
For a file-upload service, examine file type and size validation, storage permissions, malware scanning, access checks on downloads, and resource-exhaustion limits.

## Limitations
A threat model identifies plausible risks; it does not prove that a vulnerability exists. Validate important assumptions against implementation and deployment evidence.

From cellrishi-code/claude-skills-atlas, MIT.

More from cellrishi-code/claude-skills-atlas

Signals

Stars
6
Forks
6
Open issues
143
Last commit (this folder)
Oct 4, 2026 (25 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from cellrishi-code

Cite this page

threat-modeling skill. Agent Mart. https://agentmart.dev/skills/cellrishi-code-threat-modeling (last updated 2026-10-24)