kerberosmansour/hulumi / skills/hulumi-threat-model
hulumi-threat-model
FlaggedRun 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| package.json | manifest | 572 B |
| scenarios/aws-multi-account-baseline.json | config | 5.5 KB |
| scenarios/eks-cluster-baseline.json | config | 5.0 KB |
| scenarios/eks-runtime-and-backup.json | config | 4.6 KB |
| scenarios/github-actions-supply-chain.json | config | 5.9 KB |
| scenarios/github-app-token-exposure.json | config | 5.5 KB |
| scenarios/github-oidc-trust-cloud-account.json | config | 5.4 KB |
| scenarios/github-self-hosted-runner.json | config | 5.3 KB |
| scenarios/iam-least-privilege.json | config | 4.7 KB |
| scenarios/lambda-secrets-access.json | config | 5.0 KB |
| scenarios/operations-audit-pipeline-broken.json | config | 4.3 KB |
| scenarios/operations-detective-services-disabled.json | config | 4.1 KB |
| scenarios/operations-patch-compliance-lapse.json | config | 4.0 KB |
| scenarios/rds-encryption-at-rest.json | config | 4.7 KB |
| scenarios/s3-public-bucket-hardening.json | config | 4.9 KB |
| scripts/generate-threat-model.mjs | script | 22.7 KB |
| scripts/list-scenarios.mjs | script | 2.0 KB |
| templates/threat-model.template.md | markdown | 1.1 KB |
| tsconfig.json | config | 289 B |
scripts/list-scenarios.mjs
View on GitHub// list-scenarios — enumerate the prebuilt scenario IDs the skill supports.
//
// Used by:
// - the SKILL.md instructions: the agent runs this to validate a scenario
// argument before calling generate-threat-model.mjs.
// - the BDD suite: asserts the exported listScenarios() returns exactly
// the prebuilt IDs in the declared order. As of v1.1 M1 (Hulumi-for-GitHub
// 2026-04-26): 5 AWS scenarios + 4 GitHub scenarios = 9 total.
/**
* @returns {string[]} the prebuilt scenario IDs in declared order.
*/
export function listScenarios() {
// Order is a stability contract — the skill's BDD tests assert this exact
// sequence. New scenarios append at the end in future milestones.
// The 4 GitHub scenarios were added in v1.1 M1 (Hulumi-for-GitHub runbook,
// 2026-04-26) addressing the highest demand-minus-supply scenarios from
// research synthesis: (d) OIDC trust to cloud, (c) Actions supply-chain,
// (f) GitHub App / installation-token exposure, (e) self-hosted runners.
return [
"aws-multi-account-baseline",
"s3-public-bucket-hardening",
"iam-least-privilege",
"rds-encryption-at-rest",
"lambda-secrets-access",
"github-oidc-trust-cloud-account",
"github-actions-supply-chain",
"github-app-token-exposure",
"github-self-hosted-runner",
// K8s/EKS scenarios added in runbook hulumi-operations-k8s-security M6.
"eks-cluster-baseline",
"eks-runtime-and-backup",
// Operations scenarios added in runbook hulumi-operations-k8s-security M11.
"operations-patch-compliance-lapse",
"operations-detective-services-disabled",
"operations-audit-pipeline-broken",
];
}
// CLI entrypoint: `node list-scenarios.mjs` prints one scenario per line.
// Used by SKILL.md instructions to validate user input.
const isMainModule =
import.meta.url === `file://${process.argv[1]}` ||
(typeof process.argv[1] === "string" && process.argv[1].endsWith("list-scenarios.mjs"));
if (isMainModule) {
for (const id of listScenarios()) console.log(id);
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |