Cso
no-session/pstack
Chief Security Officer mode. An agent skill from no-session/pstack.
Finds security threats in a design with a STRIDE pass per component, rates severity and records fixes, with extra checks for AI agent and tool risks.
Install Threat Modeling
$ npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework threat-modeling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/security/threat-modeling .claude/skills/threat-modeling && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "threat-modeling" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/security/threat-modeling into .claude/skills/threat-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-modeling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/security/threat-modelingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework threat-modeling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/security/threat-modeling .agents/skills/threat-modeling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "threat-modeling" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/security/threat-modeling into .agents/skills/threat-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-modeling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework threat-modeling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/security/threat-modeling .cursor/skills/threat-modeling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "threat-modeling" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/security/threat-modeling into .cursor/skills/threat-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-modeling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dralgorhythm/claude-agentic-framework.git --path .claude/skills/security/threat-modeling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework threat-modeling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/security/threat-modeling .gemini/skills/threat-modeling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "threat-modeling" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/security/threat-modeling into .gemini/skills/threat-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-modeling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dralgorhythm/claude-agentic-framework threat-modelingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/security/threat-modeling .github/skills/threat-modeling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "threat-modeling" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/security/threat-modeling into .github/skills/threat-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-modeling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework threat-modeling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/security/threat-modeling .opencode/skills/threat-modeling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "threat-modeling" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/security/threat-modeling into .opencode/skills/threat-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-modeling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
threat-modeling- GitHub stars
- 125
- Token cost
- ~581 tokens
- SKILL.md length
- 233 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- None found
At a glance
Finds security threats in a design with a STRIDE pass per component, rates severity and records fixes, with extra checks for AI agent and tool risks.
- Works in 5 steps: Map Attack Surface: Use Grep and Glob to… → Enumerate Threats: Work through STRIDE… → Trace Data Flow: Use Grep to trace user… → …
- Designing a feature that touches authentication or sensitive data
- SKILL.md covers Procedure, Agent-Specific Threats and Threat Model Document
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The skill follows a five-step procedure. It maps the attack surface by searching the code for entry points and trust boundaries, sketches the data flow, then works through STRIDE (spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege) for each component. It also traces user input, authentication tokens and sensitive data from entry to storage, looking for injection and leakage points.
Each threat is rated Critical, High, Medium or Low using the definitions in the project's `.claude/rules/security.md`; Critical and High findings must be fixed before merge. Where a design has a model-and-tool boundary, it adds agent-specific threats: indirect prompt injection, tool poisoning, instruction-hierarchy violations, over-scoped tokens and config-as-code paths that run automatically on checkout. Findings are written up per asset with category, severity and remediation.
When your agent uses it
- Designing a feature that touches authentication or sensitive data
- Before implementing input-handling code
- When an audit asks for a threat model
- Reviewing an agent design that calls tools or MCP servers
Example prompts
- “Threat model the new file-upload endpoint using STRIDE.”
- “Before I build the login flow, list the threats and rate their severity.”
- “Check our MCP-based agent for prompt injection and over-scoped token risks.”
Requirements
- A project with .claude/rules/security.md defining severity levels
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Map Attack Surface: Use Grep and Glob to find entry points and trust boundaries; sketch the data flow.
- Enumerate Threats: Work through STRIDE per component — Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service…
- Trace Data Flow: Use Grep to trace user input → processing → storage, authentication token flow, and sensitive data paths, watching for…
- Rate Severity: Classify each threat as Critical / High / Medium / Low per the definitions in .claude/rules/security.md — Critical and High…
- Record Findings: Document each threat with its STRIDE category, severity, and remediation.
What it can do on your machine
Read from SKILL.md and the folder at commit 6436a20. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Threat Modeling loads about 581 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 233 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 233 words (~581 tokens).
“Beyond STRIDE, include this class whenever the design under review has a tool/model boundary:”
- name
- threat-modeling
Files
Just SKILL.md in .claude/skills/security/threat-modeling of dralgorhythm/claude-agentic-framework.
Open the folder on GitHubat commit 6436a20
Compare with similar skills
Threat Modeling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Threat Modeling this skilldralgorhythm/claude-agentic-framework | 125 | — | ~581 | Automated safety check: Pass | None | |
| Csono-session/pstack | 135 | — | ~12k | Automated safety check: Notes | MIT | |
| Security Audit Scannerruvnet/ruflo | 74k | 2 repos | ~823 | Automated safety check: Pass | MIT | |
| Forensifyalexgreensh/repo-forensics | 188 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| CSO Security Auditgarrytan/gstack | 136k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Slowmist Agent Securityslowmist/slowmist-agent-security | 508 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Security Audit Scanner
ruvnet/ruflo
Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.
Forensify
alexgreensh/repo-forensics
Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.
CSO Security Audit
garrytan/gstack
Runs an evidence-first security audit of a codebase through gstack's trusted launcher, with static findings by default and isolated reproduction when enabled.
Slowmist Agent Security
slowmist/slowmist-agent-security
Comprehensive security review framework for AI agents. An agent skill from slowmist/slowmist-agent-security.
AI SAFE2 Secure Build Copilot
CyberStrategyInstitute/ai-safe2-framework
Applies the AI SAFE2 framework to security reviews, code reviews and compliance mapping for AI agents, RAG pipelines and MCP servers.
More from dralgorhythm/claude-agentic-framework
All 20 skills in this repoSwarm Coordination
dralgorhythm/claude-agentic-framework
Rules for several agents sharing one repository: an orchestrator tracks work in two tiers, workers write to scratch files, and every handoff leaves a pointer to an artifact.
Architecture Decision Record Writer
dralgorhythm/claude-agentic-framework
Writes Architecture Decision Records with title, status, context, decision, rationale and consequences for significant technical choices, kept short and numbered.
Codebase Health Auditor
dralgorhythm/claude-agentic-framework
Runs a user-invoked, swarm-style audit of a whole codebase for SOLID and DRY violations, code smells, complexity, dead code and pattern consistency, with a prioritized report.
Dependency Upgrade Protocol
dralgorhythm/claude-agentic-framework
Sequences safe dependency upgrades: read the changelog, verify the version exists upstream, pin it, and keep major bumps in separate commits behind a full gate run.
Designing Systems
dralgorhythm/claude-agentic-framework
Produces this framework's ADR and system-design artifacts from bundled templates with trade-off analysis.
Land The Plane
dralgorhythm/claude-agentic-framework
Lands in-flight work: quality gates, atomic commit, rebase, push, verified remote sync, then handoff — a user-invoked finish-line workflow.
Related
Categories
Questions about Threat Modeling
What does Threat Modeling do?
Finds security threats in a design with a STRIDE pass per component, rates severity and records fixes, with extra checks for AI agent and tool risks. The skill follows a five-step procedure. It maps the attack surface by searching the code for entry points and trust boundaries, sketches the data flow, then works through STRIDE (spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege) for each component.
When should I use Threat Modeling?
Threat Modeling fits situations like: designing a feature that touches authentication or sensitive data; before implementing input-handling code; when an audit asks for a threat model; reviewing an agent design that calls tools or MCP servers.
How do I install Threat Modeling in Claude Code?
Run `npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a claude-code`. Or copy the skill folder (.claude/skills/security/threat-modeling in dralgorhythm/claude-agentic-framework) into .claude/skills/threat-modeling in your project. Claude Code loads it when a task matches its description.
How do I install Threat Modeling in Codex?
Run `npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a codex`. Or copy the skill folder (.claude/skills/security/threat-modeling in dralgorhythm/claude-agentic-framework) into .agents/skills/threat-modeling in your project. Codex loads it when a task matches its description.
Can I use Threat Modeling in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dralgorhythm/claude-agentic-framework --skill threat-modeling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/threat-modeling, .gemini/skills/threat-modeling, .github/skills/threat-modeling and .opencode/skills/threat-modeling in your project.
What does Threat Modeling need to run?
SKILL.md names no scripts, command-line tools or credentials: Threat Modeling is instructions for the agent only. Our summary lists: A project with .claude/rules/security.md defining severity levels.
Does Threat Modeling access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Threat Modeling safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Threat Modeling use?
No licence was found for Threat Modeling or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Threat Modeling use?
About 581 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Threat Modeling?
Skills that share tags, products or a category with Threat Modeling: Cso (no-session/pstack, 135 stars), Security Audit Scanner (ruvnet/ruflo, 74k stars), Forensify (alexgreensh/repo-forensics, 188 stars) and CSO Security Audit (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Threat Modeling?
dralgorhythm (a GitHub user) maintains it in dralgorhythm/claude-agentic-framework, which has 125 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on July 24, 2026.
Source: dralgorhythm/claude-agentic-framework on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.