[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73G5DFH3KXZS1ZY6SPKS54B":3,"skill-same:01M73G5DFH3KXZS1ZY6SPKS54B":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":62},"01M73G5DFH3KXZS1ZY6SPKS54B","stride-threat-matrix",null,"Automated STRIDE threat matrix generation and DREAD risk scoring framework for architecture, API endpoints, data flows, and infrastructure models.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-security\u002F.gemini\u002Fskills\u002Fstride-threat-matrix\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: stride-threat-matrix\ndescription: >\n  Automated STRIDE threat matrix generation and DREAD risk scoring framework\n  for architecture, API endpoints, data flows, and infrastructure models.\nversion: 1.1.0\nstatus: active\nowner: security-expert\nlast_reviewed: 2026-11-01\nprerequisites: Architecture diagrams or data flow specifications (DFD), system component inventory\nrelates_to:\n  - skill: finding-reconciliation\n    type: follows\nscope: co-security\nl2_propagate: true\nmetadata:\n  type: threat-modeling\n  triggers:\n    - stride-threat-matrix\n    - \u002Fstride-threat-matrix\n    - threat modeling\n    - dread risk scoring\n    - stride matrix\n---\n\n# 🛡️ Skill: stride-threat-matrix\n\n## Context\n\nIn security-focused engineering and threat modeling engagements (`co-security`), identifying structural vulnerabilities and prioritizing remediation requires a systematic categorization of potential threats and a reproducible risk scoring methodology.\n\n`stride-threat-matrix` provides the standard framework for automated threat classification using the **STRIDE** model combined with quantitative risk scoring via the **DREAD** framework across system architecture boundaries, API endpoints, data pipelines, and infrastructure deployments.\n\n## When to Use\n\n- Performing architectural threat modeling during {{PROJECT_PHASE_GATES}}.\n- Evaluating new service endpoints, inter-process communication (IPC) channels, or external data ingestion paths.\n- Calculating quantitative risk scores for identified design vulnerabilities before remediation planning.\n- Generating structured threat matrix artifacts for security documentation, stakeholder reviews, and audit compliance.\n\n## Execution Steps\n\n1. **System Boundary & Data Flow Decomposition**\n   - Identify system components: processes, data stores, data flows, external interconnections, and trust boundaries.\n   - Assign trust levels to each component and network boundary (e.g., untrusted ingress, semi-trusted DMZ, trusted internal core).\n\n2. **STRIDE Threat Classification**\n   For each system element and data flow, analyze and document potential threats across the six STRIDE categories:\n   - **S - Spoofing**: Authentication bypass, identity spoofing, rogue agent payload injection.\n   - **T - Tampering**: Unauthorized modification of payload data, config parameters, or memory state.\n   - **R - Repudiation**: Inadequate logging, missing audit trails, non-repudiable state mutations.\n   - **I - Information Disclosure**: Data leakage in logs, unencrypted transmission, exposed API keys or secrets.\n   - **D - Denial of Service**: Resource exhaustion, unhandled exception loops, rate limit evasion.\n   - **E - Elevation of Privilege**: Unauthorized execution rights, command injection, broken access controls.\n\n3. **DREAD Quantitative Risk Scoring**\n   Assign a score from 1 (Low) to 10 (Critical) for each of the five DREAD parameters:\n   - **Damage (D)**: How severe is the potential impact if exploited?\n   - **Reproducibility (R)**: How easy is it to reliably reproduce the exploit?\n   - **Exploitability (E)**: How much technical skill or effort is required?\n   - **Affected Users (A)**: What percentage of users\u002Fservices are impacted?\n   - **Discoverability (D)**: How easily can the threat or flaw be discovered?\n\n   Calculate the composite DREAD Risk Rating:\n   $$\\text{DREAD Score} = \\frac{D + R + E + A + D}{5}$$\n\n   Risk Classification Matrix:\n   - **Critical**: Score $\\ge 8.0$ (Requires immediate mitigation before {{PROJECT_PHASE_GATES_CRITICAL}})\n   - **High**: Score $6.0 - 7.9$ (High priority fix; security gate blocker)\n   - **Medium**: Score $4.0 - 5.9$ (Scheduled remediation in sprint cycle)\n   - **Low**: Score $\u003C 4.0$ (Documented residual risk; monitor)\n\n4. **Mitigation Control Mapping**\n   - Define concrete security controls (e.g., TLS 1.3, HMAC verification, RBAC rules, input validation gates).\n   - Verify post-mitigation residual DREAD score satisfies safety threshold ($\u003C 4.0$).\n\n5. **Artifact Generation & Output Compilation**\n   - Output the threat matrix as structured markdown and XML\u002FJSON format.\n\n## Output Format\n\n```markdown\n## STRIDE Threat Matrix & DREAD Risk Assessment\n\n**Target System**: [System \u002F Module Name]\n**Evaluation Date**: 2026-08-06\n**Evaluator**: {{PROJECT_ROLE}}\n\n### Threat Summary\n\n| ID | STRIDE Category | Threat Description | Affected Element | D | R | E | A | D | DREAD Score | Severity | Proposed Mitigation |\n|---|---|---|---|---|---|---|---|---|---|---|---|\n| THREAT-001 | Elevation of Privilege | Unauthenticated CLI invocation via IPC socket | Command Processor | 9 | 8 | 8 | 9 | 7 | 8.2 | Critical | Enforce signed auth token (verify-authorization) |\n| THREAT-002 | Information Disclosure | Plaintext token output in debug log files | Logging Subsystem | 7 | 9 | 4 | 8 | 6 | 6.8 | High | Redact authorization tokens before writing logs |\n\n### Detailed Threat Breakdown\n\n#### THREAT-001: Elevation of Privilege\n- **STRIDE Category**: Elevation of Privilege\n- **Component**: Command Processor (scripts\u002F)\n- **DREAD Calculation**: (9 + 8 + 8 + 9 + 7) \u002F 5 = **8.2 (Critical)**\n- **Mitigation Requirement**: Mandatory authentication check prior to command dispatch.\n```\n\n## Co-develop Integration Note\n\nThis file is the hub-doctrine canonical for the co-security assurance suite\n(spec 2026-11-01-hub-consolidation-design, Phase 1 batch C). Co-security\nengagements run it as written. A co-develop pipeline instance derives from this\ndoctrine by substituting the bindings below — the derivation never edits\nfrontmatter: `owner: security-expert` stays single-valued here, and the\nco-develop ownership binding lives in this note only.\n\nParameterization — unfilled placeholders resolve to the co-security doctrine\ndefaults; a co-develop derivation substitutes the bindings:\n\n| Placeholder | Instance | Unfilled default (co-security) | Co-develop binding |\n|---|---|---|---|\n| {{PROJECT_PHASE_GATES}} | When to Use, first bullet | Phase 1 security assessments | Phase 1–2 design (architect) and Phase 0\u002F5 security-monitor scans |\n| {{PROJECT_PHASE_GATES_CRITICAL}} | Risk Classification Matrix, Critical line | Phase 2 operations | Phase 4 execution |\n| {{PROJECT_ROLE}} | Output Format, `**Evaluator**` line | security-expert | security-monitor |\n\nCo-develop bindings beyond placeholders:\n\n- Ownership: co-develop renders this skill as co-owned `architect, security-monitor` (threat modeling runs during Phase 1–2 design by the architect and again in the Phase 0\u002F5 security-monitor scans). Frontmatter here stays `owner: security-expert`.\n- Engagement label: the Context sentence keeps `co-security`; a co-develop derivation reads it as `co-develop`.\n- Example mitigation text and Related Skills: co-develop omits the `verify-authorization` references (that pre-flight gate is a co-security engagement skill not adopted in the co-develop pipeline). This canonical keeps them doctrine-fixed.\n- Delivery: the co-develop fork carries `scope: common`; this canonical keeps `scope: co-security`.\n\n## Related Skills\n\n- `verify-authorization` — mandatory pre-flight gate confirming signed scope authorization.\n- `sarif-exporter` — exports generated threat findings and DREAD risk metrics into SARIF v2.1.0 JSON format.\n- `security-scan` — executes static analysis and secret detection across codebase assets.\n","# 🛡️ Skill: stride-threat-matrix\n\n## Context\n\nIn security-focused engineering and threat modeling engagements (`co-security`), identifying structural vulnerabilities and prioritizing remediation requires a systematic categorization of potential threats and a reproducible risk scoring methodology.\n\n`stride-threat-matrix` provides the standard framework for automated threat classification using the **STRIDE** model combined with quantitative risk scoring via the **DREAD** framework across system architecture boundaries, API endpoints, data pipelines, and infrastructure deployments.\n\n## When to Use\n\n- Performing architectural threat modeling during {{PROJECT_PHASE_GATES}}.\n- Evaluating new service endpoints, inter-process communication (IPC) channels, or external data ingestion paths.\n- Calculating quantitative risk scores for identified design vulnerabilities before remediation planning.\n- Generating structured threat matrix artifacts for security documentation, stakeholder reviews, and audit compliance.\n\n## Execution Steps\n\n1. **System Boundary & Data Flow Decomposition**\n   - Identify system components: processes, data stores, data flows, external interconnections, and trust boundaries.\n   - Assign trust levels to each component and network boundary (e.g., untrusted ingress, semi-trusted DMZ, trusted internal core).\n\n2. **STRIDE Threat Classification**\n   For each system element and data flow, analyze and document potential threats across the six STRIDE categories:\n   - **S - Spoofing**: Authentication bypass, identity spoofing, rogue agent payload injection.\n   - **T - Tampering**: Unauthorized modification of payload data, config parameters, or memory state.\n   - **R - Repudiation**: Inadequate logging, missing audit trails, non-repudiable state mutations.\n   - **I - Information Disclosure**: Data leakage in logs, unencrypted transmission, exposed API keys or secrets.\n   - **D - Denial of Service**: Resource exhaustion, unhandled exception loops, rate limit evasion.\n   - **E - Elevation of Privilege**: Unauthorized execution rights, command injection, broken access controls.\n\n3. **DREAD Quantitative Risk Scoring**\n   Assign a score from 1 (Low) to 10 (Critical) for each of the five DREAD parameters:\n   - **Damage (D)**: How severe is the potential impact if exploited?\n   - **Reproducibility (R)**: How easy is it to reliably reproduce the exploit?\n   - **Exploitability (E)**: How much technical skill or effort is required?\n   - **Affected Users (A)**: What percentage of users\u002Fservices are impacted?\n   - **Discoverability (D)**: How easily can the threat or flaw be discovered?\n\n   Calculate the composite DREAD Risk Rating:\n   $$\\text{DREAD Score} = \\frac{D + R + E + A + D}{5}$$\n\n   Risk Classification Matrix:\n   - **Critical**: Score $\\ge 8.0$ (Requires immediate mitigation before {{PROJECT_PHASE_GATES_CRITICAL}})\n   - **High**: Score $6.0 - 7.9$ (High priority fix; security gate blocker)\n   - **Medium**: Score $4.0 - 5.9$ (Scheduled remediation in sprint cycle)\n   - **Low**: Score $\u003C 4.0$ (Documented residual risk; monitor)\n\n4. **Mitigation Control Mapping**\n   - Define concrete security controls (e.g., TLS 1.3, HMAC verification, RBAC rules, input validation gates).\n   - Verify post-mitigation residual DREAD score satisfies safety threshold ($\u003C 4.0$).\n\n5. **Artifact Generation & Output Compilation**\n   - Output the threat matrix as structured markdown and XML\u002FJSON format.\n\n## Output Format\n\n```markdown\n## STRIDE Threat Matrix & DREAD Risk Assessment\n\n**Target System**: [System \u002F Module Name]\n**Evaluation Date**: 2026-08-06\n**Evaluator**: {{PROJECT_ROLE}}\n\n### Threat Summary\n\n| ID | STRIDE Category | Threat Description | Affected Element | D | R | E | A | D | DREAD Score | Severity | Proposed Mitigation |\n|---|---|---|---|---|---|---|---|---|---|---|---|\n| THREAT-001 | Elevation of Privilege | Unauthenticated CLI invocation via IPC socket | Command Processor | 9 | 8 | 8 | 9 | 7 | 8.2 | Critical | Enforce signed auth token (verify-authorization) |\n| THREAT-002 | Information Disclosure | Plaintext token output in debug log files | Logging Subsystem | 7 | 9 | 4 | 8 | 6 | 6.8 | High | Redact authorization tokens before writing logs |\n\n### Detailed Threat Breakdown\n\n#### THREAT-001: Elevation of Privilege\n- **STRIDE Category**: Elevation of Privilege\n- **Component**: Command Processor (scripts\u002F)\n- **DREAD Calculation**: (9 + 8 + 8 + 9 + 7) \u002F 5 = **8.2 (Critical)**\n- **Mitigation Requirement**: Mandatory authentication check prior to command dispatch.\n```\n\n## Co-develop Integration Note\n\nThis file is the hub-doctrine canonical for the co-security assurance suite\n(spec 2026-11-01-hub-consolidation-design, Phase 1 batch C). Co-security\nengagements run it as written. A co-develop pipeline instance derives from this\ndoctrine by substituting the bindings below — the derivation never edits\nfrontmatter: `owner: security-expert` stays single-valued here, and the\nco-develop ownership binding lives in this note only.\n\nParameterization — unfilled placeholders resolve to the co-security doctrine\ndefaults; a co-develop derivation substitutes the bindings:\n\n| Placeholder | Instance | Unfilled default (co-security) | Co-develop binding |\n|---|---|---|---|\n| {{PROJECT_PHASE_GATES}} | When to Use, first bullet | Phase 1 security assessments | Phase 1–2 design (architect) and Phase 0\u002F5 security-monitor scans |\n| {{PROJECT_PHASE_GATES_CRITICAL}} | Risk Classification Matrix, Critical line | Phase 2 operations | Phase 4 execution |\n| {{PROJECT_ROLE}} | Output Format, `**Evaluator**` line | security-expert | security-monitor |\n\nCo-develop bindings beyond placeholders:\n\n- Ownership: co-develop renders this skill as co-owned `architect, security-monitor` (threat modeling runs during Phase 1–2 design by the architect and again in the Phase 0\u002F5 security-monitor scans). Frontmatter here stays `owner: security-expert`.\n- Engagement label: the Context sentence keeps `co-security`; a co-develop derivation reads it as `co-develop`.\n- Example mitigation text and Related Skills: co-develop omits the `verify-authorization` references (that pre-flight gate is a co-security engagement skill not adopted in the co-develop pipeline). This canonical keeps them doctrine-fixed.\n- Delivery: the co-develop fork carries `scope: common`; this canonical keeps `scope: co-security`.\n\n## Related Skills\n\n- `verify-authorization` — mandatory pre-flight gate confirming signed scope authorization.\n- `sarif-exporter` — exports generated threat findings and DREAD risk metrics into SARIF v2.1.0 JSON format.\n- `security-scan` — executes static analysis and secret detection across codebase assets.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":34,"description":38,"l2_propagate":39,"last_reviewed":40,"prerequisites":41},"security-expert","co-security","active","1.1.0",{"type":28,"triggers":29},"threat-modeling",[5,30,31,32,33],"\u002Fstride-threat-matrix","threat modeling","dread risk scoring","stride matrix",[35],{"type":36,"skill":37},"follows","finding-reconciliation","Automated STRIDE threat matrix generation and DREAD risk scoring framework for architecture, API endpoints, data flows, and infrastructure models.\n",true,1793491200000,"Architecture diagrams or data flow specifications (DFD), system component inventory","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-security\u002F.gemini\u002Fskills\u002Fstride-threat-matrix",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":39},[52,55,58],{"tool":53,"command":54},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill stride-threat-matrix",{"tool":56,"command":57},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill stride-threat-matrix",{"tool":59,"command":60},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill stride-threat-matrix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-security\u002F.gemini\u002Fskills\u002Fstride-threat-matrix\u002FSKILL.md",[],[64,72,77,82,87,92],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":71},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":78,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":71},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":83,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":71},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":88,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":71},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":93,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":71},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]