원클릭으로
view
Display model summary with tree view of boundaries, components, data flows, and quality score
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Display model summary with tree view of boundaries, components, data flows, and quality score
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Assign classes to unclassified components, boundaries, data flows, and data items
Auto-discover infrastructure components from codebase using the infrastructure-scout agent
Guided end-to-end threat modeling workflow — scope through validation and sync
Populate security attributes, MITRE ATT&CK references, credentials, and monitoring tools
Quality dashboard with score breakdown, gap analysis, and readiness assessment
Attack surface summary with component breakdown, trust boundary crossings, and control gap analysis
| name | view |
| description | Display model summary with tree view of boundaries, components, data flows, and quality score |
| argument-hint | [model-path] [--format yaml|json|tree] |
Display a read-only summary of a Dethernety threat model.
Resolve model path:
$ARGUMENTS contains a path, use it.dethernety/models.json:
Parse format argument: Check $ARGUMENTS for --format yaml|json|tree. Default is tree.
Read model files from the resolved path:
manifest.json — model name, description, modulesstructure.json — boundary and component hierarchydataflows.json — data flow connectionsdata-items.json — data classification items.dethereal/quality.json — quality score (if exists).dethereal/state.json — current state (if exists).dethereal/sync.json — sync status (if exists)Format output based on the --format argument:
Use the model name from manifest.json as the tree header, not the internal "defaultBoundary" label. Render the default boundary's children as top-level entries.
Production Stack (56/100 quality, ENRICHING)
├── Internet Zone
│ └── [EXTERNAL_ENTITY] End Users
├── DMZ
│ └── [PROCESS] Web Server (classified: Web Application)
└── Internal Network
├── Application Tier
│ └── [PROCESS] API Server (classified: REST API)
└── Data Tier
├── [STORE] Database (classified: PostgreSQL)
└── [STORE] Cache (classified: Redis)
Data Flows (5):
1. End Users → Web Server: HTTP requests
2. Web Server → API Server: API calls (HTTPS)
3. API Server → Database: SQL queries
4. API Server → Cache: Cache lookups
5. Database → API Server: Query results
Data Items (2):
• User Credentials (classified: PII)
• Session Tokens (classified: Credentials)
Quality: 56/100 (In Progress)
Component classification: 60% (3/5 classified)
Attribute completion: 40% (2/5 with attributes)
Boundary hierarchy: 100% (depth ≥ 2, no issues)
Data flow coverage: 80% (4/5 connected)
Data classification: 50% (1/2 classified)
Sync: last pushed 2h ago | Platform model ID: abc123
Show [type] prefix for components. Show class name in parentheses if classified. Recursively render nested boundaries with tree-drawing characters.
Output the raw model data as formatted JSON, combining manifest, structure, dataflows, and data-items into a single object.
Convert the combined model data to YAML-style output. Since JSON is the canonical format (D8), this is a display convenience only.