[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-trail-of-bits-openai-security-best-practices":3,"mdc--cp0hro-key":34,"related-org-trail-of-bits-openai-security-best-practices":334,"related-repo-trail-of-bits-openai-security-best-practices":494},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"openai-security-best-practices","perform security best-practice code reviews","Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review\u002Freport, or secure-by-default coding help. Trigger only for supported languages (python, javascript\u002Ftypescript, go). Do not trigger for general code review, debugging, or non-security tasks. 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],{"name":14,"slug":15,"type":16},"Security","security","tag",{"name":18,"slug":19,"type":16},"Code Review","code-review",{"name":21,"slug":22,"type":16},"Best Practices","best-practices",460,"https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills-curated","2026-07-17T06:06:50.407352",null,29,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Curated, community-vetted Claude Code plugin marketplace","https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills-curated\u002Ftree\u002FHEAD\u002Fplugins\u002Fopenai-security-best-practices\u002Fskills\u002Fopenai-security-best-practices","---\nname: openai-security-best-practices\ndescription: Perform language and framework specific security best-practice reviews and suggest improvements.\n  Trigger only when the user explicitly requests security best practices guidance, a security review\u002Freport,\n  or secure-by-default coding help. Trigger only for supported languages (python, javascript\u002Ftypescript,\n  go). Do not trigger for general code review, debugging, or non-security tasks. Originally from OpenAI's\n  curated skills catalog.\nallowed-tools:\n- Bash\n- Read\n- Grep\n- Glob\n- Write\n- Edit\n---\n\n# Security Best Practices\n\n## Overview\n\nThis skill provides a description of how to identify the language and frameworks used by the current context, and then to load information from this skill's references directory about the security best practices for this language and or frameworks.\n\nThis information, if present, can be used to write new secure by default code, or to passively detect major issues within existing code, or (if requested by the user) provide a vulnerability report and suggest fixes.\n\n## Workflow\n\nThe initial step for this skill is to identify ALL languages and ALL frameworks which you are being asked to use or already exist in the scope of the project you are working in. Focus on the primary core frameworks. Often you will want to identify both frontend and backend languages and frameworks.\n\nThen check this skill's references directory to see if there are any relevant documentation for the language and or frameworks. Make sure you read ALL reference files which relate to the specific framework or language. The format of the filenames is `\u003Clanguage>-\u003Cframework>-\u003Cstack>-security.md`. You should also check if there is a `\u003Clanguage>-general-\u003Cstack>-security.md` which is agnostic to the framework you may be using.\n\nIf working on a web application which includes a frontend and a backend, make sure you have checked for reference documents for BOTH the frontend and backend!\n\nIf you are asked to make a web app which will include both a frontend and backend, but the frontend framework is not specified, also check out `javascript-general-web-frontend-security.md`. It is important that you understand how to secure both the frontend and backend.\n\nIf no relevant information is available in the skill's references directory, think a little bit about what you know about the language, the framework, and all well known security best practices for it. If you are unsure you can try to search online for documentation on security best practices.\n\nFrom there it can operate in a few ways.\n\n1. The primary mode is to just use the information to write secure by default code from this point forward. This is useful for starting a new project or when writing new code.\n\n2. The secondary mode is to passively detect vulnerabilities while working in the project and writing code for the user. Critical or very important vulnerabilities or major issues going against security guidance can be flagged and the user can be told about them. This passive mode should focus on the largest impact vulnerabilities and secure defaults.\n\n3. The user can ask for a security report or to improve the security of the codebase. In this case a full report should be produced describe anyways the project fails to follow security best practices guidance. The report should be prioritized and have clear sections of severity and urgency. Then offer to start working on fixes for these issues. See #fixes below.\n\n## Workflow Decision Tree\n\n- If the language\u002Fframework is unclear, inspect the repo to determine it and list your evidence.\n- If matching guidance exists in `references\u002F`, load only the relevant files and follow their instructions.\n- If no matching guidance exists, consider if you know any well known security best practices for the chosen language and or frameworks, but if asked to generate a report, let the user know that concrete guidance is not available (you can still generate the report or detect for sure critical vulnerabilities)\n\n# Overrides\n\nWhile these references contain the security best practices for languages and frameworks, customers may have cases where they need to bypass or override these practices. Pay attention to specific rules and instructions in the project's documentation and prompt files which may require you to override certain best practices. When overriding a best practice, you MAY report it to the user, but do not fight with them. If a security best practice needs to be bypassed \u002F ignored for some project specific reason, you can also suggest to add documentation about this to the project so it is clear why the best practice is not being followed and to follow that bypass in the future.\n\n# Report Format\n\nWhen producing a report, you should write the report as a markdown file in `security_best_practices_report.md` or some other location if provided by the user. You can ask the user where they would like the report to be written to.\n\nThe report should have a short executive summary at the top.\n\nThe report should be clearly delineated into multiple sections based on severity of the vulnerability. The report should focus on the most critical findings as these have the highest impact for the user. All findings should be noted with an numeric ID to make them easier to reference.\n\nFor critical findings include a one sentence impact statement.\n\nOnce the report is written, also report it to the user directly, although you may be less verbose. You can offer to explain any of the findings or the reasons behind the security best practices guidance if the user wants more info on any findings.\n\nImportant: When referencing code in the report, make sure to find and include line numbers for the code you are referencing.\n\nAfter you write the report file, summarize the findings to the user.\n\nAlso tell the user where the final report was written to\n\n# Fixes\n\nIf you produced a report, let the user read the report and ask to begin performing fixes.\n\nIf you passively found a critical finding, notify the user and ask if they would like you to fix this finding.\n\nWhen producing fixes, focus on fixing a single finding at a time. The fixes should have concise clear comments explaining that the new code is based on the specific security best practice, and perhaps a very short reason why it would be dangerous to not do it in this way.\n\nAlways consider if the changes you want to make will impact the functionality of the user's code. Consider if the changes may cause regressions with how the project works currently. It is often the case that insecure code is relied on for other reasons (and this is why insecure code lives on for so long). Avoid breaking the user's project as this may make them not want to apply security fixes in the future. It is better to write a well thought out, well informed by the rest of the project, fix, then a quick slapdash change.\n\nAlways follow any normal change or commit flow the user has configured. If making git commits, provide clear commit messages explaining this is to align with security best practices. Try to avoid bunching a number of unrelated findings into a single commit.\n\nAlways follow any normal testing flows the user has configured (if any) to confirm that your changes are not introducing regressions. Consider the second order impacts the changes may have and inform the user before making them if there are any.\n\n# General Security Advice\n\nBelow is a few bits of secure coding advice that applies to almost any language or framework.\n\n### Avoid Using Incrementing IDs for Public IDs of Resources\n\nWhen assigning an ID for some resource, which will then be used by exposed to the internet, avoid using small auto-incrementing IDs. Use longer, random UUID4 or random hex string instead. This will prevent users from learning the quantity of a resource and being able to guess resource IDs.\n\n### A note on TLS\n\nWhile TLS is important for production deployments, most development work will be with TLS disabled or provided by some out-of-scope TLS proxy. Due to this, be very careful about not reporting lack of TLS as a security issue. Also be very careful around use of \"secure\" cookies. They should only be set if the application will actually be over TLS. If they are set on non-TLS applications (such as when deployed for local dev or testing), it will break the application. You can provide a env or other flag to override setting secure as a way to keep it off until on a TLS production deployment. Additionally avoid recommending HSTS. It is dangerous to use without full understanding of the lasting impacts (can cause major outages and user lockout) and it is not generally recommended for the scope of projects being reviewed by the agent.\n\n## When to Use\n\n\u003C!-- TODO: review -->\n\n## When NOT to Use\n\n\u003C!-- TODO: review -->\n\n",{"data":35,"body":43},{"name":4,"description":6,"allowed-tools":36},[37,38,39,40,41,42],"Bash","Read","Grep","Glob","Write","Edit",{"type":44,"children":45},"root",[46,55,62,68,73,79,84,106,111,124,129,134,154,160,187,193,198,204,217,222,227,232,237,242,247,252,258,263,268,273,278,283,288,294,299,306,311,317,322,328],{"type":47,"tag":48,"props":49,"children":51},"element","h1",{"id":50},"security-best-practices",[52],{"type":53,"value":54},"text","Security Best Practices",{"type":47,"tag":56,"props":57,"children":59},"h2",{"id":58},"overview",[60],{"type":53,"value":61},"Overview",{"type":47,"tag":63,"props":64,"children":65},"p",{},[66],{"type":53,"value":67},"This skill provides a description of how to identify the language and frameworks used by the current context, and then to load information from this skill's references directory about the security best practices for this language and or frameworks.",{"type":47,"tag":63,"props":69,"children":70},{},[71],{"type":53,"value":72},"This information, if present, can be used to write new secure by default code, or to passively detect major issues within existing code, or (if requested by the user) provide a vulnerability report and suggest fixes.",{"type":47,"tag":56,"props":74,"children":76},{"id":75},"workflow",[77],{"type":53,"value":78},"Workflow",{"type":47,"tag":63,"props":80,"children":81},{},[82],{"type":53,"value":83},"The initial step for this skill is to identify ALL languages and ALL frameworks which you are being asked to use or already exist in the scope of the project you are working in. Focus on the primary core frameworks. Often you will want to identify both frontend and backend languages and frameworks.",{"type":47,"tag":63,"props":85,"children":86},{},[87,89,96,98,104],{"type":53,"value":88},"Then check this skill's references directory to see if there are any relevant documentation for the language and or frameworks. Make sure you read ALL reference files which relate to the specific framework or language. The format of the filenames is ",{"type":47,"tag":90,"props":91,"children":93},"code",{"className":92},[],[94],{"type":53,"value":95},"\u003Clanguage>-\u003Cframework>-\u003Cstack>-security.md",{"type":53,"value":97},". You should also check if there is a ",{"type":47,"tag":90,"props":99,"children":101},{"className":100},[],[102],{"type":53,"value":103},"\u003Clanguage>-general-\u003Cstack>-security.md",{"type":53,"value":105}," which is agnostic to the framework you may be using.",{"type":47,"tag":63,"props":107,"children":108},{},[109],{"type":53,"value":110},"If working on a web application which includes a frontend and a backend, make sure you have checked for reference documents for BOTH the frontend and backend!",{"type":47,"tag":63,"props":112,"children":113},{},[114,116,122],{"type":53,"value":115},"If you are asked to make a web app which will include both a frontend and backend, but the frontend framework is not specified, also check out ",{"type":47,"tag":90,"props":117,"children":119},{"className":118},[],[120],{"type":53,"value":121},"javascript-general-web-frontend-security.md",{"type":53,"value":123},". It is important that you understand how to secure both the frontend and backend.",{"type":47,"tag":63,"props":125,"children":126},{},[127],{"type":53,"value":128},"If no relevant information is available in the skill's references directory, think a little bit about what you know about the language, the framework, and all well known security best practices for it. If you are unsure you can try to search online for documentation on security best practices.",{"type":47,"tag":63,"props":130,"children":131},{},[132],{"type":53,"value":133},"From there it can operate in a few ways.",{"type":47,"tag":135,"props":136,"children":137},"ol",{},[138,144,149],{"type":47,"tag":139,"props":140,"children":141},"li",{},[142],{"type":53,"value":143},"The primary mode is to just use the information to write secure by default code from this point forward. This is useful for starting a new project or when writing new code.",{"type":47,"tag":139,"props":145,"children":146},{},[147],{"type":53,"value":148},"The secondary mode is to passively detect vulnerabilities while working in the project and writing code for the user. Critical or very important vulnerabilities or major issues going against security guidance can be flagged and the user can be told about them. This passive mode should focus on the largest impact vulnerabilities and secure defaults.",{"type":47,"tag":139,"props":150,"children":151},{},[152],{"type":53,"value":153},"The user can ask for a security report or to improve the security of the codebase. In this case a full report should be produced describe anyways the project fails to follow security best practices guidance. The report should be prioritized and have clear sections of severity and urgency. Then offer to start working on fixes for these issues. See #fixes below.",{"type":47,"tag":56,"props":155,"children":157},{"id":156},"workflow-decision-tree",[158],{"type":53,"value":159},"Workflow Decision Tree",{"type":47,"tag":161,"props":162,"children":163},"ul",{},[164,169,182],{"type":47,"tag":139,"props":165,"children":166},{},[167],{"type":53,"value":168},"If the language\u002Fframework is unclear, inspect the repo to determine it and list your evidence.",{"type":47,"tag":139,"props":170,"children":171},{},[172,174,180],{"type":53,"value":173},"If matching guidance exists in ",{"type":47,"tag":90,"props":175,"children":177},{"className":176},[],[178],{"type":53,"value":179},"references\u002F",{"type":53,"value":181},", load only the relevant files and follow their instructions.",{"type":47,"tag":139,"props":183,"children":184},{},[185],{"type":53,"value":186},"If no matching guidance exists, consider if you know any well known security best practices for the chosen language and or frameworks, but if asked to generate a report, let the user know that concrete guidance is not available (you can still generate the report or detect for sure critical vulnerabilities)",{"type":47,"tag":48,"props":188,"children":190},{"id":189},"overrides",[191],{"type":53,"value":192},"Overrides",{"type":47,"tag":63,"props":194,"children":195},{},[196],{"type":53,"value":197},"While these references contain the security best practices for languages and frameworks, customers may have cases where they need to bypass or override these practices. Pay attention to specific rules and instructions in the project's documentation and prompt files which may require you to override certain best practices. When overriding a best practice, you MAY report it to the user, but do not fight with them. If a security best practice needs to be bypassed \u002F ignored for some project specific reason, you can also suggest to add documentation about this to the project so it is clear why the best practice is not being followed and to follow that bypass in the future.",{"type":47,"tag":48,"props":199,"children":201},{"id":200},"report-format",[202],{"type":53,"value":203},"Report Format",{"type":47,"tag":63,"props":205,"children":206},{},[207,209,215],{"type":53,"value":208},"When producing a report, you should write the report as a markdown file in ",{"type":47,"tag":90,"props":210,"children":212},{"className":211},[],[213],{"type":53,"value":214},"security_best_practices_report.md",{"type":53,"value":216}," or some other location if provided by the user. You can ask the user where they would like the report to be written to.",{"type":47,"tag":63,"props":218,"children":219},{},[220],{"type":53,"value":221},"The report should have a short executive summary at the top.",{"type":47,"tag":63,"props":223,"children":224},{},[225],{"type":53,"value":226},"The report should be clearly delineated into multiple sections based on severity of the vulnerability. The report should focus on the most critical findings as these have the highest impact for the user. All findings should be noted with an numeric ID to make them easier to reference.",{"type":47,"tag":63,"props":228,"children":229},{},[230],{"type":53,"value":231},"For critical findings include a one sentence impact statement.",{"type":47,"tag":63,"props":233,"children":234},{},[235],{"type":53,"value":236},"Once the report is written, also report it to the user directly, although you may be less verbose. You can offer to explain any of the findings or the reasons behind the security best practices guidance if the user wants more info on any findings.",{"type":47,"tag":63,"props":238,"children":239},{},[240],{"type":53,"value":241},"Important: When referencing code in the report, make sure to find and include line numbers for the code you are referencing.",{"type":47,"tag":63,"props":243,"children":244},{},[245],{"type":53,"value":246},"After you write the report file, summarize the findings to the user.",{"type":47,"tag":63,"props":248,"children":249},{},[250],{"type":53,"value":251},"Also tell the user where the final report was written to",{"type":47,"tag":48,"props":253,"children":255},{"id":254},"fixes",[256],{"type":53,"value":257},"Fixes",{"type":47,"tag":63,"props":259,"children":260},{},[261],{"type":53,"value":262},"If you produced a report, let the user read the report and ask to begin performing fixes.",{"type":47,"tag":63,"props":264,"children":265},{},[266],{"type":53,"value":267},"If you passively found a critical finding, notify the user and ask if they would like you to fix this finding.",{"type":47,"tag":63,"props":269,"children":270},{},[271],{"type":53,"value":272},"When producing fixes, focus on fixing a single finding at a time. The fixes should have concise clear comments explaining that the new code is based on the specific security best practice, and perhaps a very short reason why it would be dangerous to not do it in this way.",{"type":47,"tag":63,"props":274,"children":275},{},[276],{"type":53,"value":277},"Always consider if the changes you want to make will impact the functionality of the user's code. Consider if the changes may cause regressions with how the project works currently. It is often the case that insecure code is relied on for other reasons (and this is why insecure code lives on for so long). Avoid breaking the user's project as this may make them not want to apply security fixes in the future. It is better to write a well thought out, well informed by the rest of the project, fix, then a quick slapdash change.",{"type":47,"tag":63,"props":279,"children":280},{},[281],{"type":53,"value":282},"Always follow any normal change or commit flow the user has configured. If making git commits, provide clear commit messages explaining this is to align with security best practices. Try to avoid bunching a number of unrelated findings into a single commit.",{"type":47,"tag":63,"props":284,"children":285},{},[286],{"type":53,"value":287},"Always follow any normal testing flows the user has configured (if any) to confirm that your changes are not introducing regressions. Consider the second order impacts the changes may have and inform the user before making them if there are any.",{"type":47,"tag":48,"props":289,"children":291},{"id":290},"general-security-advice",[292],{"type":53,"value":293},"General Security Advice",{"type":47,"tag":63,"props":295,"children":296},{},[297],{"type":53,"value":298},"Below is a few bits of secure coding advice that applies to almost any language or framework.",{"type":47,"tag":300,"props":301,"children":303},"h3",{"id":302},"avoid-using-incrementing-ids-for-public-ids-of-resources",[304],{"type":53,"value":305},"Avoid Using Incrementing IDs for Public IDs of Resources",{"type":47,"tag":63,"props":307,"children":308},{},[309],{"type":53,"value":310},"When assigning an ID for some resource, which will then be used by exposed to the internet, avoid using small auto-incrementing IDs. Use longer, random UUID4 or random hex string instead. This will prevent users from learning the quantity of a resource and being able to guess resource IDs.",{"type":47,"tag":300,"props":312,"children":314},{"id":313},"a-note-on-tls",[315],{"type":53,"value":316},"A note on TLS",{"type":47,"tag":63,"props":318,"children":319},{},[320],{"type":53,"value":321},"While TLS is important for production deployments, most development work will be with TLS disabled or provided by some out-of-scope TLS proxy. Due to this, be very careful about not reporting lack of TLS as a security issue. Also be very careful around use of \"secure\" cookies. They should only be set if the application will actually be over TLS. If they are set on non-TLS applications (such as when deployed for local dev or testing), it will break the application. You can provide a env or other flag to override setting secure as a way to keep it off until on a TLS production deployment. Additionally avoid recommending HSTS. It is dangerous to use without full understanding of the lasting impacts (can cause major outages and user lockout) and it is not generally recommended for the scope of projects being reviewed by the agent.",{"type":47,"tag":56,"props":323,"children":325},{"id":324},"when-to-use",[326],{"type":53,"value":327},"When to Use",{"type":47,"tag":56,"props":329,"children":331},{"id":330},"when-not-to-use",[332],{"type":53,"value":333},"When NOT to Use",{"items":335,"total":493},[336,355,365,385,400,413,425,435,448,459,471,482],{"slug":337,"name":337,"fn":338,"description":339,"org":340,"tags":341,"stars":352,"repoUrl":353,"updatedAt":354},"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},[342,345,348,349],{"name":343,"slug":344,"type":16},"C#","c",{"name":346,"slug":347,"type":16},"Debugging","debugging",{"name":14,"slug":15,"type":16},{"name":350,"slug":351,"type":16},"Testing","testing",6139,"https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills","2026-07-17T06:05:14.925095",{"slug":356,"name":356,"fn":357,"description":358,"org":359,"tags":360,"stars":352,"repoUrl":353,"updatedAt":364},"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},[361,362,363],{"name":343,"slug":344,"type":16},{"name":14,"slug":15,"type":16},{"name":350,"slug":351,"type":16},"2026-07-17T06:05:12.433192",{"slug":366,"name":366,"fn":367,"description":368,"org":369,"tags":370,"stars":352,"repoUrl":353,"updatedAt":384},"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},[371,374,377,380,383],{"name":372,"slug":373,"type":16},"Agents","agents",{"name":375,"slug":376,"type":16},"CI\u002FCD","ci-cd",{"name":378,"slug":379,"type":16},"Code Analysis","code-analysis",{"name":381,"slug":382,"type":16},"GitHub Actions","github-actions",{"name":14,"slug":15,"type":16},"2026-07-18T05:47:48.564744",{"slug":386,"name":386,"fn":387,"description":388,"org":389,"tags":390,"stars":352,"repoUrl":353,"updatedAt":399},"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},[391,394,395,396],{"name":392,"slug":393,"type":16},"Audit","audit",{"name":378,"slug":379,"type":16},{"name":14,"slug":15,"type":16},{"name":397,"slug":398,"type":16},"Smart Contracts","smart-contracts","2026-07-18T05:47:43.989063",{"slug":401,"name":401,"fn":402,"description":403,"org":404,"tags":405,"stars":352,"repoUrl":353,"updatedAt":412},"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},[406,409],{"name":407,"slug":408,"type":16},"Engineering","engineering",{"name":410,"slug":411,"type":16},"Productivity","productivity","2026-07-17T06:05:33.543262",{"slug":414,"name":414,"fn":415,"description":416,"org":417,"tags":418,"stars":352,"repoUrl":353,"updatedAt":424},"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},[419,422,423],{"name":420,"slug":421,"type":16},"Python","python",{"name":14,"slug":15,"type":16},{"name":350,"slug":351,"type":16},"2026-07-17T06:05:14.575191",{"slug":426,"name":426,"fn":427,"description":428,"org":429,"tags":430,"stars":352,"repoUrl":353,"updatedAt":434},"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},[431,432,433],{"name":392,"slug":393,"type":16},{"name":378,"slug":379,"type":16},{"name":14,"slug":15,"type":16},"2026-08-01T05:44:54.920542",{"slug":436,"name":436,"fn":437,"description":438,"org":439,"tags":440,"stars":352,"repoUrl":353,"updatedAt":447},"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},[441,444,445,446],{"name":442,"slug":443,"type":16},"Architecture","architecture",{"name":392,"slug":393,"type":16},{"name":378,"slug":379,"type":16},{"name":407,"slug":408,"type":16},"2026-07-18T05:47:40.122449",{"slug":449,"name":449,"fn":450,"description":451,"org":452,"tags":453,"stars":352,"repoUrl":353,"updatedAt":458},"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},[454,455,456,457],{"name":392,"slug":393,"type":16},{"name":378,"slug":379,"type":16},{"name":407,"slug":408,"type":16},{"name":14,"slug":15,"type":16},"2026-07-18T05:47:39.210985",{"slug":460,"name":460,"fn":461,"description":462,"org":463,"tags":464,"stars":352,"repoUrl":353,"updatedAt":470},"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},[465,466,469],{"name":392,"slug":393,"type":16},{"name":467,"slug":468,"type":16},"CLI","cli",{"name":14,"slug":15,"type":16},"2026-07-17T06:05:33.198077",{"slug":472,"name":472,"fn":473,"description":474,"org":475,"tags":476,"stars":352,"repoUrl":353,"updatedAt":481},"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},[477,478,479,480],{"name":392,"slug":393,"type":16},{"name":343,"slug":344,"type":16},{"name":378,"slug":379,"type":16},{"name":14,"slug":15,"type":16},"2026-07-17T06:05:11.333374",{"slug":483,"name":483,"fn":484,"description":485,"org":486,"tags":487,"stars":352,"repoUrl":353,"updatedAt":492},"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},[488,489,490,491],{"name":392,"slug":393,"type":16},{"name":378,"slug":379,"type":16},{"name":14,"slug":15,"type":16},{"name":397,"slug":398,"type":16},"2026-07-18T05:47:42.84568",111,{"items":495,"total":596},[496,506,516,535,547,563,577],{"slug":497,"name":497,"fn":498,"description":499,"org":500,"tags":501,"stars":23,"repoUrl":24,"updatedAt":505},"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},[502,503,504],{"name":378,"slug":379,"type":16},{"name":14,"slug":15,"type":16},{"name":350,"slug":351,"type":16},"2026-07-17T06:05:08.247908",{"slug":507,"name":507,"fn":508,"description":509,"org":510,"tags":511,"stars":23,"repoUrl":24,"updatedAt":515},"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},[512,513,514],{"name":378,"slug":379,"type":16},{"name":346,"slug":347,"type":16},{"name":14,"slug":15,"type":16},"2026-07-18T05:47:30.015093",{"slug":517,"name":517,"fn":518,"description":519,"org":520,"tags":521,"stars":23,"repoUrl":24,"updatedAt":534},"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},[522,525,528,531],{"name":523,"slug":524,"type":16},"Analysis","analysis",{"name":526,"slug":527,"type":16},"Coaching","coaching",{"name":529,"slug":530,"type":16},"Ideation","ideation",{"name":532,"slug":533,"type":16},"Strategy","strategy","2026-07-18T05:48:12.46583",{"slug":536,"name":536,"fn":537,"description":538,"org":539,"tags":540,"stars":23,"repoUrl":24,"updatedAt":546},"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},[541,542,545],{"name":372,"slug":373,"type":16},{"name":543,"slug":544,"type":16},"Context","context",{"name":410,"slug":411,"type":16},"2026-07-18T05:47:03.196098",{"slug":548,"name":548,"fn":549,"description":550,"org":551,"tags":552,"stars":23,"repoUrl":24,"updatedAt":562},"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},[553,556,559],{"name":554,"slug":555,"type":16},"Content Creation","content-creation",{"name":557,"slug":558,"type":16},"Editing","editing",{"name":560,"slug":561,"type":16},"Writing","writing","2026-07-18T05:47:18.1749",{"slug":564,"name":564,"fn":565,"description":566,"org":567,"tags":568,"stars":23,"repoUrl":24,"updatedAt":576},"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},[569,570,573],{"name":523,"slug":524,"type":16},{"name":571,"slug":572,"type":16},"Research","research",{"name":574,"slug":575,"type":16},"Social Media","social-media","2026-07-17T06:04:39.744471",{"slug":578,"name":578,"fn":579,"description":580,"org":581,"tags":582,"stars":23,"repoUrl":24,"updatedAt":595},"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},[583,586,589,592],{"name":584,"slug":585,"type":16},"Cloudflare","cloudflare",{"name":587,"slug":588,"type":16},"Cloudflare Pages","cloudflare-pages",{"name":590,"slug":591,"type":16},"Cloudflare Workers","cloudflare-workers",{"name":593,"slug":594,"type":16},"Deployment","deployment","2026-07-17T06:04:46.574433",31]