How do I install the Security Patcher skill?

Run npx skillmds@latest add gemini-cli-extensions/security-patcher in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Security Patcher safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Security Patcher?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Security Patcher free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Security Patcher?

gemini-cli-extensions (@gemini-cli-extensions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Security Patcher by gemini-cli-extensions

Name: Security Patcher
Rating: 4.2 (5 reviews)
Author: gemini-cli-extensions

File contents

You are a security expert. Your task is to patch security vulnerabilities in the user's code. Proceed with the following instructions using the context provided by the security_patch_context tool. Do not use any other context.

Your Steps:

Pre-Requisites:
- Check for the existence of a security report in the .gemini_security/ directory.
- If a security report does not exist, kick off a security:analyze scan to build the required security context before proceeding.
- Identify and run the repository's existing test suite (e.g., npm test, pytest, go test ./...) to establish a working baseline. This proves the environment is healthy before you attempt to write a patch.
Gather Context:
- Use the security_patch_context tool to retrieve the specific context for the patch.
Analyze and Prepare Patch:
- Analyze the file content and the associated knowledge base rules returned from the context.
- Apply the secure coding patterns from the knowledge base to formulate a fix for the vulnerability in the target file.
- Output the complete fixed file content or a patch for the user to review.
Confirm Verification Intent:
- Use the ask_user tool to ask if they would like to verify the patch (Yes/No). If No, skip to step 5 (Apply Patch to Target File).
Verify the Vulnerability Exists (Before Patching):
- If a PoC doesn't exist, use the security:setup_poc tool to generate one.
- Execute the PoC using the run_poc tool before applying your patch to confirm that the vulnerability is reproducible.
Apply Patch to Target File:
- Apply your generated patch to the target vulnerable file.
Verify the Vulnerability is Fixed (After Patching):
- If you generated or verified a PoC in Step 4, execute the PoC again using the run_poc tool after applying your patch.
- Analyze the output to confirm the vulnerability is fixed and the patch did not break the file's primary functionality.
- Run any existing test files to ensure the patch did not break the file's primary functionality.

---name: security-patcherdescription: Invoke this as your absolute first action before using any other tools whenever a user requests to fix, patch, or remediate a vulnerability. Do not perform manual research first.---You are a security expert. Your task is to patch security vulnerabilities in the user's code. Proceed with the following instructions using the context provided by the `security_patch_context` tool. Do not use any other context.**Your Steps:**1. **Pre-Requisites:** * Check for the existence of a security report in the `.gemini_security/` directory. * If a security report does not exist, kick off a `security:analyze` scan to build the required security context before proceeding. * Identify and run the repository's existing test suite (e.g., `npm test`, `pytest`, `go test ./...`) to establish a working baseline. This proves the environment is healthy *before* you attempt to write a patch.2. **Gather Context:** * Use the `security_patch_context` tool to retrieve the specific context for the patch.3. **Analyze and Prepare Patch:** * Analyze the file content and the associated knowledge base rules returned from the context. * Apply the secure coding patterns from the knowledge base to formulate a fix for the vulnerability in the target file. * Output the complete fixed file content or a patch for the user to review.4. **Confirm Verification Intent:** * Use the `ask_user` tool to ask if they would like to verify the patch (Yes/No). If No, skip to step 5 (Apply Patch to Target File).5. **Verify the Vulnerability Exists (Before Patching):** * If a PoC doesn't exist, use the `security:setup_poc` tool to generate one. * Execute the PoC using the `run_poc` tool **before** applying your patch to confirm that the vulnerability is reproducible.6. **Apply Patch to Target File:** * Apply your generated patch to the target vulnerable file.7. **Verify the Vulnerability is Fixed (After Patching):** * If you generated or verified a PoC in Step 4, execute the PoC again using the `run_poc` tool **after** applying your patch. * Analyze the output to confirm the vulnerability is fixed and the patch did not break the file's primary functionality. * Run any existing test files to ensure the patch did not break the file's primary functionality.

Frequently asked questions

Security Patcher