[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72BBDC1P55DR5W4TMTDMFBP":3,"skill-same:01M72BBDC1P55DR5W4TMTDMFBP":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72BBDC1P55DR5W4TMTDMFBP","security-threat-model",null,"Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats\u002Fabuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.","guhans6\u002Fagent-workbench","guhans6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104162539?v=4","01M72B46KNSP1Y4W32NAP9HSCS","Guhan","01M72B46MCE81N1B04M3PWX3P7",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsecurity-threat-model\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsecurity-threat-model\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: \"security-threat-model\"\ndescription: \"Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats\u002Fabuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.\"\n---\n\n# Threat Model Source Code Repo\n\nDeliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.\n\n## Quick start\n\n1) Collect (or infer) inputs:\n- Repo root path and any in-scope paths.\n- Intended usage, deployment model, internet exposure, and auth expectations (if known).\n- Any existing repository summary or architecture spec.\n- Use prompts in `references\u002Fprompt-template.md` to generate a repository summary.\n- Follow the required output contract in `references\u002Fprompt-template.md`. Use it verbatim when possible.\n\n## Workflow\n\n### 1) Scope and extract the system model\n- Identify primary components, data stores, and external integrations from the repo summary.\n- Identify how the system runs (server, CLI, library, worker) and its entrypoints.\n- Separate runtime behavior from CI\u002Fbuild\u002Fdev tooling and from tests\u002Fexamples.\n- Map the in-scope locations to those components and exclude out-of-scope items explicitly.\n- Do not claim components, flows, or controls without evidence.\n\n### 2) Derive boundaries, assets, and entry points\n- Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.\n- List assets that drive risk (data, credentials, models, config, compute resources, audit logs).\n- Identify entry points (endpoints, upload surfaces, parsers\u002Fdecoders, job triggers, admin tooling, logging\u002Ferror sinks).\n\n### 3) Calibrate assets and attacker capabilities\n- List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).\n- Describe realistic attacker capabilities based on exposure and intended usage.\n- Explicitly note non-capabilities to avoid inflated severity.\n\n\n### 4) Enumerate threats as abuse paths\n- Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).\n- Classify each threat and tie it to impacted assets.\n- Keep the number of threats small but high quality.\n\n### 5) Prioritize with explicit likelihood and impact reasoning\n- Use qualitative likelihood and impact (low\u002Fmedium\u002Fhigh) with short justifications.\n- Set overall priority (critical\u002Fhigh\u002Fmedium\u002Flow) using likelihood x impact, adjusted for existing controls.\n- State which assumptions most influence the ranking.\n\n### 6) Validate service context and assumptions with the user\n- Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.\n- Ask 1–3 targeted questions to resolve missing context (service owner and environment, scale\u002Fusers, deployment model, authn\u002Fauthz, internet exposure, data sensitivity, multi-tenancy).\n- Pause and wait for user feedback before producing the final report.\n- If the user declines or can’t answer, state which assumptions remain and how they influence priority.\n\n### 7) Recommend mitigations and focus paths\n- Distinguish existing mitigations (with evidence) from recommended mitigations.\n- Tie mitigations to concrete locations (component, boundary, or entry point) and control types (authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging).\n- Prefer specific implementation hints over generic advice (e.g., \"enforce schema at gateway for upload payloads\" vs \"validate inputs\").\n- Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.\n\n### 8) Run a quality check before finalizing\n- Confirm all discovered entrypoints are covered.\n- Confirm each trust boundary is represented in threats.\n- Confirm runtime vs CI\u002Fdev separation.\n- Confirm user clarifications (or explicit non-responses) are reflected.\n- Confirm assumptions and open questions are explicit.\n- Confirm that the format of the report matches closely the required output format defined in prompt template: `references\u002Fprompt-template.md`\n- Write the final Markdown to a file named `\u003Crepo-or-dir-name>-threat-model.md` (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).\n\n\n## Risk prioritization guidance (illustrative, not exhaustive)\n- High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.\n- Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log\u002Fmetrics poisoning that affects detection.\n- Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.\n\n## References\n\n- Output contract and full prompt template: `references\u002Fprompt-template.md`\n- Optional controls\u002Fasset list: `references\u002Fsecurity-controls-and-assets.md`\n\nOnly load the reference files you need. Keep the final result concise, grounded, and reviewable.\n","# Threat Model Source Code Repo\n\nDeliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.\n\n## Quick start\n\n1) Collect (or infer) inputs:\n- Repo root path and any in-scope paths.\n- Intended usage, deployment model, internet exposure, and auth expectations (if known).\n- Any existing repository summary or architecture spec.\n- Use prompts in `references\u002Fprompt-template.md` to generate a repository summary.\n- Follow the required output contract in `references\u002Fprompt-template.md`. Use it verbatim when possible.\n\n## Workflow\n\n### 1) Scope and extract the system model\n- Identify primary components, data stores, and external integrations from the repo summary.\n- Identify how the system runs (server, CLI, library, worker) and its entrypoints.\n- Separate runtime behavior from CI\u002Fbuild\u002Fdev tooling and from tests\u002Fexamples.\n- Map the in-scope locations to those components and exclude out-of-scope items explicitly.\n- Do not claim components, flows, or controls without evidence.\n\n### 2) Derive boundaries, assets, and entry points\n- Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.\n- List assets that drive risk (data, credentials, models, config, compute resources, audit logs).\n- Identify entry points (endpoints, upload surfaces, parsers\u002Fdecoders, job triggers, admin tooling, logging\u002Ferror sinks).\n\n### 3) Calibrate assets and attacker capabilities\n- List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).\n- Describe realistic attacker capabilities based on exposure and intended usage.\n- Explicitly note non-capabilities to avoid inflated severity.\n\n\n### 4) Enumerate threats as abuse paths\n- Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).\n- Classify each threat and tie it to impacted assets.\n- Keep the number of threats small but high quality.\n\n### 5) Prioritize with explicit likelihood and impact reasoning\n- Use qualitative likelihood and impact (low\u002Fmedium\u002Fhigh) with short justifications.\n- Set overall priority (critical\u002Fhigh\u002Fmedium\u002Flow) using likelihood x impact, adjusted for existing controls.\n- State which assumptions most influence the ranking.\n\n### 6) Validate service context and assumptions with the user\n- Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.\n- Ask 1–3 targeted questions to resolve missing context (service owner and environment, scale\u002Fusers, deployment model, authn\u002Fauthz, internet exposure, data sensitivity, multi-tenancy).\n- Pause and wait for user feedback before producing the final report.\n- If the user declines or can’t answer, state which assumptions remain and how they influence priority.\n\n### 7) Recommend mitigations and focus paths\n- Distinguish existing mitigations (with evidence) from recommended mitigations.\n- Tie mitigations to concrete locations (component, boundary, or entry point) and control types (authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging).\n- Prefer specific implementation hints over generic advice (e.g., \"enforce schema at gateway for upload payloads\" vs \"validate inputs\").\n- Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.\n\n### 8) Run a quality check before finalizing\n- Confirm all discovered entrypoints are covered.\n- Confirm each trust boundary is represented in threats.\n- Confirm runtime vs CI\u002Fdev separation.\n- Confirm user clarifications (or explicit non-responses) are reflected.\n- Confirm assumptions and open questions are explicit.\n- Confirm that the format of the report matches closely the required output format defined in prompt template: `references\u002Fprompt-template.md`\n- Write the final Markdown to a file named `\u003Crepo-or-dir-name>-threat-model.md` (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).\n\n\n## Risk prioritization guidance (illustrative, not exhaustive)\n- High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.\n- Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log\u002Fmetrics poisoning that affects detection.\n- Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.\n\n## References\n\n- Output contract and full prompt template: `references\u002Fprompt-template.md`\n- Optional controls\u002Fasset list: `references\u002Fsecurity-controls-and-assets.md`\n\nOnly load the reference files you need. Keep the final result concise, grounded, and reviewable.\n",{"name":5,"description":7},"main","46b2e9493d75c07ea357cf5ac24ec104afb55500","shared\u002Fskills\u002Fsecurity-threat-model","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench","https:\u002F\u002Fgithub.com\u002Fguhans6","2026-10-11 17:12:57",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add guhans6\u002Fagent-workbench --skill security-threat-model",{"tool":37,"command":38},"bunx","bunx skills add guhans6\u002Fagent-workbench --skill security-threat-model",{"tool":40,"command":41},"pnpm","pnpm dlx skills add guhans6\u002Fagent-workbench --skill security-threat-model","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsecurity-threat-model\u002FSKILL.md",true,[45,51,56,60],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",254,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsecurity-threat-model\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10776,{"path":57,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fprompt-template.md",12642,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsecurity-threat-model\u002Freferences\u002Fprompt-template.md",{"path":61,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fsecurity-controls-and-assets.md",1680,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsecurity-threat-model\u002Freferences\u002Fsecurity-controls-and-assets.md",[65,73,82,90,98,105],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":20},"01M72BDFZ4DSFCX7RHGN6NTMMB","winui-app","Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M72BD9EFCTBR28FEBJQQRVS8","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","MIT","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M72BD5GWQYR251PE9T29GXFR","transcribe","Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio\u002Fvideo, extract text from recordings, or label speakers in interviews or meetings.","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Ftranscribe\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Ftranscribe\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M72BD2GFD6AS2J1J24940AN4","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fto-tickets\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M72BCN5R8AD3FQKFXRXKETJC","swiftui-pro","Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswiftui-pro\u002Fskills\u002Fswiftui-pro\u002FSKILL.md",[],[],{"skillNo":106,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M72BCJXF6ZWD25F8FGASNSAK","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswiftui-pro\u002FSKILL.md",[],[]]