[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-trail-of-bits-openai-security-threat-model":3,"mdc--vw2yvi-key":37,"related-org-trail-of-bits-openai-security-threat-model":448,"related-repo-trail-of-bits-openai-security-threat-model":606},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"openai-security-threat-model","generate repository threat models","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. Originally from OpenAI's curated skills catalog.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"trail-of-bits","Trail of Bits","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Ftrail-of-bits.png","trailofbits",[13,17,20,23],{"name":14,"slug":15,"type":16},"Security","security","tag",{"name":18,"slug":19,"type":16},"Markdown","markdown",{"name":21,"slug":22,"type":16},"Threat Modeling","threat-modeling",{"name":24,"slug":25,"type":16},"Code Analysis","code-analysis",460,"https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills-curated","2026-07-17T06:05:10.58741",null,29,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"Curated, community-vetted Claude Code plugin marketplace","https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills-curated\u002Ftree\u002FHEAD\u002Fplugins\u002Fopenai-security-threat-model\u002Fskills\u002Fopenai-security-threat-model","---\nname: openai-security-threat-model\ndescription: Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities,\n  abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user\n  explicitly asks to threat model a codebase or path, enumerate threats\u002Fabuse paths, or perform AppSec\n  threat modeling. Do not trigger for general architecture summaries, code review, or non-security design\n  work. Originally from OpenAI's curated skills catalog.\nallowed-tools:\n- Read\n- Grep\n- Glob\n- Write\n- Edit\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\n## When to Use\n\n\u003C!-- TODO: review -->\n\n## When NOT to Use\n\n\u003C!-- TODO: review -->\n\n",{"data":38,"body":45},{"name":4,"description":6,"allowed-tools":39},[40,41,42,43,44],"Read","Grep","Glob","Write","Edit",{"type":46,"children":47},"root",[48,57,63,70,80,125,131,138,166,172,190,196,214,220,238,244,262,268,291,297,320,326,377,383,401,407,431,436,442],{"type":49,"tag":50,"props":51,"children":53},"element","h1",{"id":52},"threat-model-source-code-repo",[54],{"type":55,"value":56},"text","Threat Model Source Code Repo",{"type":49,"tag":58,"props":59,"children":60},"p",{},[61],{"type":55,"value":62},"Deliver 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.",{"type":49,"tag":64,"props":65,"children":67},"h2",{"id":66},"quick-start",[68],{"type":55,"value":69},"Quick start",{"type":49,"tag":71,"props":72,"children":73},"ol",{},[74],{"type":49,"tag":75,"props":76,"children":77},"li",{},[78],{"type":55,"value":79},"Collect (or infer) inputs:",{"type":49,"tag":81,"props":82,"children":83},"ul",{},[84,89,94,99,113],{"type":49,"tag":75,"props":85,"children":86},{},[87],{"type":55,"value":88},"Repo root path and any in-scope paths.",{"type":49,"tag":75,"props":90,"children":91},{},[92],{"type":55,"value":93},"Intended usage, deployment model, internet exposure, and auth expectations (if known).",{"type":49,"tag":75,"props":95,"children":96},{},[97],{"type":55,"value":98},"Any existing repository summary or architecture spec.",{"type":49,"tag":75,"props":100,"children":101},{},[102,104,111],{"type":55,"value":103},"Use prompts in ",{"type":49,"tag":105,"props":106,"children":108},"code",{"className":107},[],[109],{"type":55,"value":110},"references\u002Fprompt-template.md",{"type":55,"value":112}," to generate a repository summary.",{"type":49,"tag":75,"props":114,"children":115},{},[116,118,123],{"type":55,"value":117},"Follow the required output contract in ",{"type":49,"tag":105,"props":119,"children":121},{"className":120},[],[122],{"type":55,"value":110},{"type":55,"value":124},". Use it verbatim when possible.",{"type":49,"tag":64,"props":126,"children":128},{"id":127},"workflow",[129],{"type":55,"value":130},"Workflow",{"type":49,"tag":132,"props":133,"children":135},"h3",{"id":134},"_1-scope-and-extract-the-system-model",[136],{"type":55,"value":137},"1) Scope and extract the system model",{"type":49,"tag":81,"props":139,"children":140},{},[141,146,151,156,161],{"type":49,"tag":75,"props":142,"children":143},{},[144],{"type":55,"value":145},"Identify primary components, data stores, and external integrations from the repo summary.",{"type":49,"tag":75,"props":147,"children":148},{},[149],{"type":55,"value":150},"Identify how the system runs (server, CLI, library, worker) and its entrypoints.",{"type":49,"tag":75,"props":152,"children":153},{},[154],{"type":55,"value":155},"Separate runtime behavior from CI\u002Fbuild\u002Fdev tooling and from tests\u002Fexamples.",{"type":49,"tag":75,"props":157,"children":158},{},[159],{"type":55,"value":160},"Map the in-scope locations to those components and exclude out-of-scope items explicitly.",{"type":49,"tag":75,"props":162,"children":163},{},[164],{"type":55,"value":165},"Do not claim components, flows, or controls without evidence.",{"type":49,"tag":132,"props":167,"children":169},{"id":168},"_2-derive-boundaries-assets-and-entry-points",[170],{"type":55,"value":171},"2) Derive boundaries, assets, and entry points",{"type":49,"tag":81,"props":173,"children":174},{},[175,180,185],{"type":49,"tag":75,"props":176,"children":177},{},[178],{"type":55,"value":179},"Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.",{"type":49,"tag":75,"props":181,"children":182},{},[183],{"type":55,"value":184},"List assets that drive risk (data, credentials, models, config, compute resources, audit logs).",{"type":49,"tag":75,"props":186,"children":187},{},[188],{"type":55,"value":189},"Identify entry points (endpoints, upload surfaces, parsers\u002Fdecoders, job triggers, admin tooling, logging\u002Ferror sinks).",{"type":49,"tag":132,"props":191,"children":193},{"id":192},"_3-calibrate-assets-and-attacker-capabilities",[194],{"type":55,"value":195},"3) Calibrate assets and attacker capabilities",{"type":49,"tag":81,"props":197,"children":198},{},[199,204,209],{"type":49,"tag":75,"props":200,"children":201},{},[202],{"type":55,"value":203},"List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).",{"type":49,"tag":75,"props":205,"children":206},{},[207],{"type":55,"value":208},"Describe realistic attacker capabilities based on exposure and intended usage.",{"type":49,"tag":75,"props":210,"children":211},{},[212],{"type":55,"value":213},"Explicitly note non-capabilities to avoid inflated severity.",{"type":49,"tag":132,"props":215,"children":217},{"id":216},"_4-enumerate-threats-as-abuse-paths",[218],{"type":55,"value":219},"4) Enumerate threats as abuse paths",{"type":49,"tag":81,"props":221,"children":222},{},[223,228,233],{"type":49,"tag":75,"props":224,"children":225},{},[226],{"type":55,"value":227},"Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).",{"type":49,"tag":75,"props":229,"children":230},{},[231],{"type":55,"value":232},"Classify each threat and tie it to impacted assets.",{"type":49,"tag":75,"props":234,"children":235},{},[236],{"type":55,"value":237},"Keep the number of threats small but high quality.",{"type":49,"tag":132,"props":239,"children":241},{"id":240},"_5-prioritize-with-explicit-likelihood-and-impact-reasoning",[242],{"type":55,"value":243},"5) Prioritize with explicit likelihood and impact reasoning",{"type":49,"tag":81,"props":245,"children":246},{},[247,252,257],{"type":49,"tag":75,"props":248,"children":249},{},[250],{"type":55,"value":251},"Use qualitative likelihood and impact (low\u002Fmedium\u002Fhigh) with short justifications.",{"type":49,"tag":75,"props":253,"children":254},{},[255],{"type":55,"value":256},"Set overall priority (critical\u002Fhigh\u002Fmedium\u002Flow) using likelihood x impact, adjusted for existing controls.",{"type":49,"tag":75,"props":258,"children":259},{},[260],{"type":55,"value":261},"State which assumptions most influence the ranking.",{"type":49,"tag":132,"props":263,"children":265},{"id":264},"_6-validate-service-context-and-assumptions-with-the-user",[266],{"type":55,"value":267},"6) Validate service context and assumptions with the user",{"type":49,"tag":81,"props":269,"children":270},{},[271,276,281,286],{"type":49,"tag":75,"props":272,"children":273},{},[274],{"type":55,"value":275},"Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.",{"type":49,"tag":75,"props":277,"children":278},{},[279],{"type":55,"value":280},"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).",{"type":49,"tag":75,"props":282,"children":283},{},[284],{"type":55,"value":285},"Pause and wait for user feedback before producing the final report.",{"type":49,"tag":75,"props":287,"children":288},{},[289],{"type":55,"value":290},"If the user declines or can’t answer, state which assumptions remain and how they influence priority.",{"type":49,"tag":132,"props":292,"children":294},{"id":293},"_7-recommend-mitigations-and-focus-paths",[295],{"type":55,"value":296},"7) Recommend mitigations and focus paths",{"type":49,"tag":81,"props":298,"children":299},{},[300,305,310,315],{"type":49,"tag":75,"props":301,"children":302},{},[303],{"type":55,"value":304},"Distinguish existing mitigations (with evidence) from recommended mitigations.",{"type":49,"tag":75,"props":306,"children":307},{},[308],{"type":55,"value":309},"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).",{"type":49,"tag":75,"props":311,"children":312},{},[313],{"type":55,"value":314},"Prefer specific implementation hints over generic advice (e.g., \"enforce schema at gateway for upload payloads\" vs \"validate inputs\").",{"type":49,"tag":75,"props":316,"children":317},{},[318],{"type":55,"value":319},"Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.",{"type":49,"tag":132,"props":321,"children":323},{"id":322},"_8-run-a-quality-check-before-finalizing",[324],{"type":55,"value":325},"8) Run a quality check before finalizing",{"type":49,"tag":81,"props":327,"children":328},{},[329,334,339,344,349,354,364],{"type":49,"tag":75,"props":330,"children":331},{},[332],{"type":55,"value":333},"Confirm all discovered entrypoints are covered.",{"type":49,"tag":75,"props":335,"children":336},{},[337],{"type":55,"value":338},"Confirm each trust boundary is represented in threats.",{"type":49,"tag":75,"props":340,"children":341},{},[342],{"type":55,"value":343},"Confirm runtime vs CI\u002Fdev separation.",{"type":49,"tag":75,"props":345,"children":346},{},[347],{"type":55,"value":348},"Confirm user clarifications (or explicit non-responses) are reflected.",{"type":49,"tag":75,"props":350,"children":351},{},[352],{"type":55,"value":353},"Confirm assumptions and open questions are explicit.",{"type":49,"tag":75,"props":355,"children":356},{},[357,359],{"type":55,"value":358},"Confirm that the format of the report matches closely the required output format defined in prompt template: ",{"type":49,"tag":105,"props":360,"children":362},{"className":361},[],[363],{"type":55,"value":110},{"type":49,"tag":75,"props":365,"children":366},{},[367,369,375],{"type":55,"value":368},"Write the final Markdown to a file named ",{"type":49,"tag":105,"props":370,"children":372},{"className":371},[],[373],{"type":55,"value":374},"\u003Crepo-or-dir-name>-threat-model.md",{"type":55,"value":376}," (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).",{"type":49,"tag":64,"props":378,"children":380},{"id":379},"risk-prioritization-guidance-illustrative-not-exhaustive",[381],{"type":55,"value":382},"Risk prioritization guidance (illustrative, not exhaustive)",{"type":49,"tag":81,"props":384,"children":385},{},[386,391,396],{"type":49,"tag":75,"props":387,"children":388},{},[389],{"type":55,"value":390},"High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.",{"type":49,"tag":75,"props":392,"children":393},{},[394],{"type":55,"value":395},"Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log\u002Fmetrics poisoning that affects detection.",{"type":49,"tag":75,"props":397,"children":398},{},[399],{"type":55,"value":400},"Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.",{"type":49,"tag":64,"props":402,"children":404},{"id":403},"references",[405],{"type":55,"value":406},"References",{"type":49,"tag":81,"props":408,"children":409},{},[410,420],{"type":49,"tag":75,"props":411,"children":412},{},[413,415],{"type":55,"value":414},"Output contract and full prompt template: ",{"type":49,"tag":105,"props":416,"children":418},{"className":417},[],[419],{"type":55,"value":110},{"type":49,"tag":75,"props":421,"children":422},{},[423,425],{"type":55,"value":424},"Optional controls\u002Fasset list: ",{"type":49,"tag":105,"props":426,"children":428},{"className":427},[],[429],{"type":55,"value":430},"references\u002Fsecurity-controls-and-assets.md",{"type":49,"tag":58,"props":432,"children":433},{},[434],{"type":55,"value":435},"Only load the reference files you need. Keep the final result concise, grounded, and reviewable.",{"type":49,"tag":64,"props":437,"children":439},{"id":438},"when-to-use",[440],{"type":55,"value":441},"When to Use",{"type":49,"tag":64,"props":443,"children":445},{"id":444},"when-not-to-use",[446],{"type":55,"value":447},"When NOT to Use",{"items":449,"total":605},[450,469,479,497,512,525,537,547,560,571,583,594],{"slug":451,"name":451,"fn":452,"description":453,"org":454,"tags":455,"stars":466,"repoUrl":467,"updatedAt":468},"address-sanitizer","detect memory errors during fuzzing","AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C\u002FC++ code to find buffer overflows and use-after-free bugs.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[456,459,462,463],{"name":457,"slug":458,"type":16},"C#","c",{"name":460,"slug":461,"type":16},"Debugging","debugging",{"name":14,"slug":15,"type":16},{"name":464,"slug":465,"type":16},"Testing","testing",6139,"https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills","2026-07-17T06:05:14.925095",{"slug":470,"name":470,"fn":471,"description":472,"org":473,"tags":474,"stars":466,"repoUrl":467,"updatedAt":478},"aflpp","perform multi-core fuzzing of C\u002FC++ projects","AFL++ is a fork of AFL with better fuzzing performance and advanced features. Use for multi-core fuzzing of C\u002FC++ projects.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[475,476,477],{"name":457,"slug":458,"type":16},{"name":14,"slug":15,"type":16},{"name":464,"slug":465,"type":16},"2026-07-17T06:05:12.433192",{"slug":480,"name":480,"fn":481,"description":482,"org":483,"tags":484,"stars":466,"repoUrl":467,"updatedAt":496},"agentic-actions-auditor","audit GitHub Actions for security vulnerabilities","Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI\u002FCD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI\u002FCD pipeline security for prompt injection risks, or evaluating agentic action configurations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[485,488,491,492,495],{"name":486,"slug":487,"type":16},"Agents","agents",{"name":489,"slug":490,"type":16},"CI\u002FCD","ci-cd",{"name":24,"slug":25,"type":16},{"name":493,"slug":494,"type":16},"GitHub Actions","github-actions",{"name":14,"slug":15,"type":16},"2026-07-18T05:47:48.564744",{"slug":498,"name":498,"fn":499,"description":500,"org":501,"tags":502,"stars":466,"repoUrl":467,"updatedAt":511},"algorand-vulnerability-scanner","scan Algorand smart contracts for vulnerabilities","Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL\u002FPyTeal).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[503,506,507,508],{"name":504,"slug":505,"type":16},"Audit","audit",{"name":24,"slug":25,"type":16},{"name":14,"slug":15,"type":16},{"name":509,"slug":510,"type":16},"Smart Contracts","smart-contracts","2026-07-18T05:47:43.989063",{"slug":513,"name":513,"fn":514,"description":515,"org":516,"tags":517,"stars":466,"repoUrl":467,"updatedAt":524},"ask-questions-if-underspecified","clarify requirements before implementation","Clarify requirements before implementing. Use when serious doubts arise.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[518,521],{"name":519,"slug":520,"type":16},"Engineering","engineering",{"name":522,"slug":523,"type":16},"Productivity","productivity","2026-07-17T06:05:33.543262",{"slug":526,"name":526,"fn":527,"description":528,"org":529,"tags":530,"stars":466,"repoUrl":467,"updatedAt":536},"atheris","fuzz Python code with Atheris","Atheris is a coverage-guided Python fuzzer based on libFuzzer. Use for fuzzing pure Python code and Python C extensions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[531,534,535],{"name":532,"slug":533,"type":16},"Python","python",{"name":14,"slug":15,"type":16},{"name":464,"slug":465,"type":16},"2026-07-17T06:05:14.575191",{"slug":538,"name":538,"fn":539,"description":540,"org":541,"tags":542,"stars":466,"repoUrl":467,"updatedAt":546},"audit-augmentation","augment code graphs with audit findings","Augments Trailmark code graphs with external audit findings from SARIF static analysis results, weAudit annotation files, and version-gated Trailmark 0.4.x binary-analysis graph exports. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, importing binary graph findings, cross-referencing Semgrep, CodeQL, or binary-analysis findings with call graph data, or visualizing audit findings in the context of code structure.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[543,544,545],{"name":504,"slug":505,"type":16},{"name":24,"slug":25,"type":16},{"name":14,"slug":15,"type":16},"2026-08-01T05:44:54.920542",{"slug":548,"name":548,"fn":549,"description":550,"org":551,"tags":552,"stars":466,"repoUrl":467,"updatedAt":559},"audit-context-building","build architectural context for code analysis","Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[553,556,557,558],{"name":554,"slug":555,"type":16},"Architecture","architecture",{"name":504,"slug":505,"type":16},{"name":24,"slug":25,"type":16},{"name":519,"slug":520,"type":16},"2026-07-18T05:47:40.122449",{"slug":561,"name":561,"fn":562,"description":563,"org":564,"tags":565,"stars":466,"repoUrl":467,"updatedAt":570},"audit-prep-assistant","prepare codebases for security audits","Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[566,567,568,569],{"name":504,"slug":505,"type":16},{"name":24,"slug":25,"type":16},{"name":519,"slug":520,"type":16},{"name":14,"slug":15,"type":16},"2026-07-18T05:47:39.210985",{"slug":572,"name":572,"fn":573,"description":574,"org":575,"tags":576,"stars":466,"repoUrl":467,"updatedAt":582},"burpsuite-project-parser","parse Burp Suite project files","Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[577,578,581],{"name":504,"slug":505,"type":16},{"name":579,"slug":580,"type":16},"CLI","cli",{"name":14,"slug":15,"type":16},"2026-07-17T06:05:33.198077",{"slug":584,"name":584,"fn":585,"description":586,"org":587,"tags":588,"stars":466,"repoUrl":467,"updatedAt":593},"c-review","audit C and C++ code","Performs comprehensive C\u002FC++ security review for memory corruption, integer overflows, race conditions, and platform-specific vulnerabilities. Use when auditing native C\u002FC++ applications, reviewing daemons or services for memory safety, or hunting integer overflow \u002F use-after-free \u002F race conditions in userspace code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[589,590,591,592],{"name":504,"slug":505,"type":16},{"name":457,"slug":458,"type":16},{"name":24,"slug":25,"type":16},{"name":14,"slug":15,"type":16},"2026-07-17T06:05:11.333374",{"slug":595,"name":595,"fn":596,"description":597,"org":598,"tags":599,"stars":466,"repoUrl":467,"updatedAt":604},"cairo-vulnerability-scanner","scan Cairo and StarkNet contracts for vulnerabilities","Scans Cairo\u002FStarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[600,601,602,603],{"name":504,"slug":505,"type":16},{"name":24,"slug":25,"type":16},{"name":14,"slug":15,"type":16},{"name":509,"slug":510,"type":16},"2026-07-18T05:47:42.84568",111,{"items":607,"total":708},[608,618,628,647,659,675,689],{"slug":609,"name":609,"fn":610,"description":611,"org":612,"tags":613,"stars":26,"repoUrl":27,"updatedAt":617},"ffuf-web-fuzzing","perform web fuzzing with ffuf","Expert guidance for ffuf web fuzzing during authorized penetration testing. Covers directory discovery, subdomain enumeration, parameter fuzzing, authenticated fuzzing with raw requests, auto-calibration, and result analysis. Use when running ffuf scans, analyzing ffuf output, or building fuzzing strategies for web targets.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[614,615,616],{"name":24,"slug":25,"type":16},{"name":14,"slug":15,"type":16},{"name":464,"slug":465,"type":16},"2026-07-17T06:05:08.247908",{"slug":619,"name":619,"fn":620,"description":621,"org":622,"tags":623,"stars":26,"repoUrl":27,"updatedAt":627},"ghidra-headless","reverse engineer binaries with Ghidra","Reverse engineers binaries using Ghidra's headless analyzer. Use when decompiling executables, extracting functions, strings, symbols, or analyzing call graphs from compiled binaries without the Ghidra GUI.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[624,625,626],{"name":24,"slug":25,"type":16},{"name":460,"slug":461,"type":16},{"name":14,"slug":15,"type":16},"2026-07-18T05:47:30.015093",{"slug":629,"name":629,"fn":630,"description":631,"org":632,"tags":633,"stars":26,"repoUrl":27,"updatedAt":646},"grilling","stress-test plans and decisions","Interviews the user relentlessly about a plan, decision, or idea until every branch of the decision tree is resolved. Use when the user wants to stress-test their thinking, sharpen a plan or design before acting, or uses any 'grill' trigger phrase (e.g. \"grill me on this\").",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[634,637,640,643],{"name":635,"slug":636,"type":16},"Analysis","analysis",{"name":638,"slug":639,"type":16},"Coaching","coaching",{"name":641,"slug":642,"type":16},"Ideation","ideation",{"name":644,"slug":645,"type":16},"Strategy","strategy","2026-07-18T05:48:12.46583",{"slug":648,"name":648,"fn":649,"description":650,"org":651,"tags":652,"stars":26,"repoUrl":27,"updatedAt":658},"handoff","compact conversation for session handoff","Compacts the current conversation into a handoff document so a fresh agent can continue the work in a new session.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[653,654,657],{"name":486,"slug":487,"type":16},{"name":655,"slug":656,"type":16},"Context","context",{"name":522,"slug":523,"type":16},"2026-07-18T05:47:03.196098",{"slug":660,"name":660,"fn":661,"description":662,"org":663,"tags":664,"stars":26,"repoUrl":27,"updatedAt":674},"humanizer","edit text to sound human-written","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, negative\nparallelisms, and excessive conjunctive phrases. 30c5c8d (Update humanizer plugin to upstream v2.2.0)\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[665,668,671],{"name":666,"slug":667,"type":16},"Content Creation","content-creation",{"name":669,"slug":670,"type":16},"Editing","editing",{"name":672,"slug":673,"type":16},"Writing","writing","2026-07-18T05:47:18.1749",{"slug":676,"name":676,"fn":677,"description":678,"org":679,"tags":680,"stars":26,"repoUrl":27,"updatedAt":688},"last30days","research recent community discussions and trends","Researches a topic from the last 30 days on Reddit, X, and the web. Surfaces real community discussions with engagement metrics and synthesizes findings into actionable insights. Use when the user wants to know what people are saying about a topic right now.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[681,682,685],{"name":635,"slug":636,"type":16},{"name":683,"slug":684,"type":16},"Research","research",{"name":686,"slug":687,"type":16},"Social Media","social-media","2026-07-17T06:04:39.744471",{"slug":690,"name":690,"fn":691,"description":692,"org":693,"tags":694,"stars":26,"repoUrl":27,"updatedAt":707},"openai-cloudflare-deploy","deploy applications to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare. Originally from OpenAI's curated skills catalog.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[695,698,701,704],{"name":696,"slug":697,"type":16},"Cloudflare","cloudflare",{"name":699,"slug":700,"type":16},"Cloudflare Pages","cloudflare-pages",{"name":702,"slug":703,"type":16},"Cloudflare Workers","cloudflare-workers",{"name":705,"slug":706,"type":16},"Deployment","deployment","2026-07-17T06:04:46.574433",31]