Skip to content

kerberosmansour/hulumi / skills/hulumi-threat-model

hulumi-threat-model

Flagged

Run an AWS or GitHub cloud / platform threat model for a specific Hulumi scenario. Produces a structured markdown threat-model document at docs/threat-model-<scenario>-<date>.md in the user's working directory, citing CSA CCM v4.1, NIST SP 800-53 Rev 5, NIST SP 800-218A, MITRE ATLAS v5.1, CIS AWS Foundations v5.0.0, CIS GitHub Benchmark v1.2.0, NIST SSDF v1.1, OpenSSF Scorecard, MITRE ATT&CK T1195, and GitHub Well-Architected SSDF by framework ID only (no verbatim control text). Use when the user asks for a threat model for an AWS or GitHub scenario, wants to ground IaC design decisions in standard controls, or wants to see which @hulumi/baseline components apply.

templates/threat-model.template.md

View on GitHub
---
name: threat-model-{{SCENARIO_ID}}
scenario: {{SCENARIO_ID}}
generated_at: {{GENERATED_AT}}
citations:
{{CITATIONS}}
---

# Threat Model — {{SCENARIO_TITLE}}

> Generated by the [`/hulumi-threat-model`](https://github.com/kerberosmansour/hulumi) Claude Code skill. This document cites CSA CCM v4.1, CIS AWS Foundations Benchmark v5.0.0, NIST SP 800-53 Rev 5, NIST SP 800-218 / 218A, and MITRE ATLAS v5.1 by **identifier only**. See [`docs/mappings/licensing.md`](https://github.com/kerberosmansour/hulumi/blob/main/docs/mappings/licensing.md) for the IDs-only policy.

## Scenario

{{SCENARIO_DESCRIPTION}}

## Actors

{{ACTORS}}

## Assets

{{ASSETS}}

## Threats (STRIDE)

| Type | Name | Description | Controls |
|---|---|---|---|
{{STRIDE_ROWS}}

## Control Citations

| Framework | ID | URL |
|---|---|---|
{{CITATION_ROWS}}

## Recommended Hulumi Components

{{COMPONENTS}}

## Open Questions

{{OPEN_QUESTIONS}}

---

_Generated `{{GENERATED_AT}}` by `/hulumi-threat-model {{SCENARIO_ID}}`. Audit footer: this document was produced without embedding verbatim framework text; any framework prose above is paraphrase authored by Hulumi maintainers._
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall