pre-threat-model

Maps application attack surfaces and trust boundaries to prepare structured threat models for bug bounty targets.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/mccleod1290/bb-agentic-setupv2 --skill pre-threat-model-mccleod1290
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-threat-model
Source: https://github.com/mccleod1290/bb-agentic-setupv2/tree/main/web-skills/pre-threat-model
Command: npx skills add https://github.com/mccleod1290/bb-agentic-setupv2 --skill pre-threat-model-mccleod1290

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security researchers often jump into testing without a structured understanding of the target, wasting time on low-impact paths. This Skill guides a disciplined 5-step attack surface mapping process that converts recon data into a pre-threat model, so every subsequent test ties back to a crown jewel and provable impact. ## Core Features & Use Cases - 5-Step Attack Surface Mapping: Walks through application architecture, mechanisms and trust boundaries, notable objects, security controls, and crown jewels with nightmare scenarios. - Trust Boundary Analysis: Identifies what the backend assumes about each request, distinguishing session-derived ownership from client-supplied IDs (IDOR-prone) across login, password reset, CRUD, upload, and webhook mechanisms. - Security Control Enumeration: Documents CSP, cookie flags, CSRF, CORS, and JWT validation per subdomain to determine which attack classes are viable versus blocked. - Use Case: After running recon on a bug bounty target, feed the recon-data inventory into this Skill to produce understanding-app.md and threat-model/pre-threat-model.md, which then feed directly into STRIDE threat modeling and hypothesis generation. ## Quick Start Ask the assistant to run the pre-threat-model skill against your target application name or URL to generate a structured attack surface map from your recon data.

Frequently Asked Questions about pre-threat-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map an application's attack surface before threat modeling?▼

Follow a 5-step process: document architecture and tech stack, enumerate mechanisms and their trust boundaries, identify notable objects and field discrepancies, catalog security controls per subdomain, and define crown jewels with nightmare scenarios. This skill guides each step and outputs structured Markdown.

What is a trust boundary in web application security testing?▼

A trust boundary is any point where the backend makes assumptions about a request, such as trusting a session token, a client-supplied ID, or an OAuth redirect. Mechanisms like password reset have more open boundaries than login, and client-supplied ownership IDs signal IDOR opportunities.

How do I identify IDOR vulnerabilities during recon?▼

Check whether ownership is session-derived or client-supplied. Endpoints using usernames or IDs from the URL path or request body are IDOR-prone if the server only validates that a session exists, not that the session user owns the requested resource.

What is the response-to-request attack technique?▼

Send a request with a few fields, observe the response returning many more fields, then copy the entire response object back into the request body. Test each extra field for server-side acceptance, especially boolean control-flow fields like is_admin or email_validated in Node.js apps.

Does this skill work without existing recon data?▼

It is designed to consume recon output such as endpoint inventories, auth contexts, and security control observations from notes/{target}/recon-data/. Without recon data it can still guide manual analysis, but it will not invent endpoints or roles absent from provided sources.

When should I deprioritize an attack path in a threat model?▼

Deprioritize paths blocked by strong controls, such as strict CSP with nonces, HTTP-only SameSite=Strict cookies, or session-derived ownership, unless a bypass exists. Invest first where controls are weak and the path leads toward a crown jewel or cross-tenant impact.