Fla Ascend Performance
fla-org/flash-linear-attention
Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.
Remediate security findings by producing minimal, surgical code patches.
Install Threat Patch
$ npx skills add pproenca/dot-skills --skill threat-patch -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills threat-patch --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/threat-patch .claude/skills/threat-patch && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "threat-patch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/threat-patch into .claude/skills/threat-patch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-patch", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/threat-patchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill threat-patch -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills threat-patch --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/threat-patch .agents/skills/threat-patch && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "threat-patch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/threat-patch into .agents/skills/threat-patch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-patch", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill threat-patch -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills threat-patch --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/threat-patch .cursor/skills/threat-patch && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "threat-patch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/threat-patch into .cursor/skills/threat-patch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-patch", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/threat-patch--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill threat-patch -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills threat-patch --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/threat-patch .gemini/skills/threat-patch && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "threat-patch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/threat-patch into .gemini/skills/threat-patch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-patch", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills threat-patchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill threat-patch -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/threat-patch .github/skills/threat-patch && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "threat-patch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/threat-patch into .github/skills/threat-patch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-patch", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill threat-patch -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills threat-patch --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/threat-patch .opencode/skills/threat-patch && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "threat-patch" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/threat-patch into .opencode/skills/threat-patch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-patch", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
threat-patch- GitHub stars
- 215
- Token cost
- ~1.3k tokens
- SKILL.md length
- 527 words
- Files
- 9 (incl. scripts, references)
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- MIT
At a glance
Remediate security findings by producing minimal, surgical code patches.
- Works in 5 steps: Read workflow for the detailed patching… → Read fix patterns when designing fixes —… → Read output format for the documentation… → …
- Patch security findings
- SKILL.md covers When to Apply, Input Sources (priority order), Workflow Overview and How to Use, plus 4 more sections
- Runs Shell scripts from its folder; calls git
What it does
Threat Patch is an agent skill from pproenca/dot-skills. Remediate security findings by producing minimal, surgical code patches. Triggers on 'patch security findings', 'fix vulnerabilities', 'remediate findings', 'threat patch', or when the user provides a findings.json (from threat-model), a Codex security findings CSV, a THREAT-MODEL.md, or individual vulnerability descriptions and wants them fixed. Also trigger when reviewing code flagged by a security scanner and the user wants actionable fixes rather than just reports.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `config.json`, `gotchas.md` and `hooks/hooks.json`).
It sits in Security, covering Threat modeling, Vulnerability scanning and CSV and tabular files. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Patch security findings
- Fix vulnerabilities
- Remediate findings
- The user provides a findings.json (from threat-model)
Example prompts
- “patch security findings”
- “fix vulnerabilities”
- “remediate findings”
- “/threat-patch”
Requirements
- A Bash shell
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read workflow for the detailed patching methodology at each step
- Read fix patterns when designing fixes — common patterns by vulnerability class
- Read output format for the documentation template per patch
- If input is findings.json: read it directly — it's already structured
- If input is Codex CSV: run scripts/parse-findings.sh to extract structured output
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Threat Patch loads about 1.3k tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 527 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 527 words, ~1,347 tokens.
Download SKILL.mdSave it as
.claude/skills/threat-patch/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- threat-patch
- description
- Remediate security findings by producing minimal, surgical code patches. Triggers on 'patch security findings', 'fix vulnerabilities', 'remediate findings', 'threat patch', or when the user provides a findings.json (from threat-model), a Codex security findings CSV, a THREAT-MODEL.md, or individual vulnerability descriptions and wants them fixed. Also trigger when reviewing code flagged by a security scanner and the user wants actionable fixes rather than just reports.
Threat Patch
Reads security findings and produces minimal, surgical code patches with structured documentation. Fixes are code-grounded — each patch targets specific files and functions identified in the finding. Output includes a summary, validation steps, and the code changes.
When to Apply
- User provides a
findings.json(from threat-model) and wants fixes - User provides a Codex security findings CSV and wants fixes
- User has a THREAT-MODEL.md and wants to remediate identified risks
- User describes a specific vulnerability and wants a patch
- Reviewing security scanner output and needs actionable fixes
- After a security audit, turning findings into code changes
Input Sources (priority order)
| Source | What It Provides | How to Use |
|---|---|---|
| findings.json (from threat-model) | Structured findings with data flow traces, systemic groupings, exploit chains, and severity ratings | Read directly — richest input, already triaged and grouped |
| Codex CSV | Title, description, severity, relevant_paths per finding | Run scripts/parse-findings.sh <csv-path> to extract structured output |
| THREAT-MODEL.md | Human-readable threat model | Extract findings from Criticality Calibration section |
| Inline description | User describes a specific vulnerability | Parse from conversation context |
When findings.json is available, it's the preferred input — it includes data flow traces (entry → chain → sink) that directly inform where to apply fixes, and systemic groupings that suggest centralized fixes over individual patches.
Workflow Overview
1. Ingest Findings → Read findings.json / CSV / descriptions
2. Triage & Group → Sort by severity, use systemic groupings if available
3. For each finding:
a. Read Code → Open relevant_paths, understand the pattern
b. Confirm → Verify issue is still present in HEAD
c. Design Fix → Determine minimal fix approach
d. Implement → Write the code changes
e. Document → Summary + Validation + Attack-path (if needed)
f. Test → Run relevant tests
4. Output → Per-patch deliverable with summary and diff
5. Update State → Mark patched findings in findings.json (if present)How to Use
- Read workflow for the detailed patching methodology at each step
- Read fix patterns when designing fixes — common patterns by vulnerability class
- Read output format for the documentation template per patch
- If input is findings.json: read it directly — it's already structured
- If input is Codex CSV: run
scripts/parse-findings.sh <csv-path>to extract structured output
Show full SKILL.md (265 more words)Show less
Key Principles
- Minimal diff: Fix the vulnerability, don't refactor surrounding code. The smallest correct patch is the best patch
- Centralize over duplicate: When multiple code paths share the same vulnerability pattern, extract a shared helper rather than patching each site independently
- Explicit error paths: Add specific error types for rejected inputs with clear operator feedback, not silent failures or generic errors
- Confirm before fixing: Always verify the finding is still present in HEAD — code may have moved or been refactored since the finding was detected
- User approval before edits: Present the fix design (files to change, approach) and wait for approval before modifying source code. Hooks gate Edit/Write tool calls for additional safety
- Document even failures: When a fix can't be tested due to environment limitations, document the test command and the limitation
Guardrails
This skill modifies source code. Safety measures:
- PreToolUse hooks on Edit and Write tools prompt for confirmation before each file change
- Confirmation gate in the workflow between fix design and implementation
- Revert path: Without commits (default), use
git checkout -- <files>to undo. With commits, usegit revert
Output Modes
Code patch — when a fix is implemented:
- Summary of what was confirmed and what the fix does
- Testing section with build/test commands
- The actual code changes
Analysis only — when the fix needs user decision or architectural changes:
- Summary of what was confirmed
- Validation checklist
- Attack-path analysis (path, likelihood, impact, assumptions, controls, blindspots)
References
| File | When to Read |
|---|---|
| references/workflow.md | Before starting — detailed approach for each patching phase |
| references/fix-patterns.md | When designing fixes — patterns by vulnerability class |
| references/output-format.md | When documenting — templates for both output modes |
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (scripts, references) in skills/.experimental/threat-patch of pproenca/dot-skills.
- SKILL.md
- config.json
- gotchas.md
- hooks/hooks.json
- metadata.json
- references/fix-patterns.md
- references/output-format.md
- references/workflow.md
- scripts/parse-findings.sh
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Threat Patch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Threat Patch this skillpproenca/dot-skills | 215 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Fla Ascend Performancefla-org/flash-linear-attention | 5.8k | — | ~6.3k | Automated safety check: Pass | MIT | |
| Forensifyalexgreensh/repo-forensics | 188 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| Senior SecurityLeoYeAI/openclaw-master-skills | 2.2k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Security Ownership Mapdiegosouzapw/awesome-omni-skills | 159 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Defender Easmvinayaklatthe/microsoft-security-skills | 175 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Forensify
alexgreensh/repo-forensics
Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.
Senior Security
LeoYeAI/openclaw-master-skills
Security engineering toolkit for threat modeling, vulnerability analysis, secure architecture, and penetration testing.
Security Ownership Map
diegosouzapw/awesome-omni-skills
Security Ownership Map workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Defender Easm
vinayaklatthe/microsoft-security-skills
Guidance for Microsoft Defender External Attack Surface Management (Defender EASM) — discovers and inventories an organization's internet-facing assets (domains, hosts, IPs, SSL certs, ASNs, web…
Vulnerability Scanner
Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Advanced vulnerability analysis principles. An agent skill from Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI.
More from pproenca/dot-skills
All 41 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Categories
Questions about Threat Patch
What does Threat Patch do?
Remediate security findings by producing minimal, surgical code patches. Threat Patch is an agent skill from pproenca/dot-skills. Remediate security findings by producing minimal, surgical code patches.
When should I use Threat Patch?
Threat Patch fits situations like: patch security findings; fix vulnerabilities; remediate findings; the user provides a findings.json (from threat-model).
How do I install Threat Patch in Claude Code?
Run `npx skills add pproenca/dot-skills --skill threat-patch -a claude-code`. Or copy the skill folder (skills/.experimental/threat-patch in pproenca/dot-skills) into .claude/skills/threat-patch in your project. Claude Code loads it when a task matches its description.
How do I install Threat Patch in Codex?
Run `npx skills add pproenca/dot-skills --skill threat-patch -a codex`. Or copy the skill folder (skills/.experimental/threat-patch in pproenca/dot-skills) into .agents/skills/threat-patch in your project. Codex loads it when a task matches its description.
Can I use Threat Patch in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill threat-patch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/threat-patch, .gemini/skills/threat-patch, .github/skills/threat-patch and .opencode/skills/threat-patch in your project.
What does Threat Patch need to run?
Going by SKILL.md and its folder, Threat Patch needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.
Does Threat Patch access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Threat Patch safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Threat Patch use?
Threat Patch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Threat Patch use?
About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.6k tokens, read only when the agent opens those files.
What are the alternatives to Threat Patch?
Skills that share tags, products or a category with Threat Patch: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Forensify (alexgreensh/repo-forensics, 188 stars), Senior Security (LeoYeAI/openclaw-master-skills, 2.2k stars) and Security Ownership Map (diegosouzapw/awesome-omni-skills, 159 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Threat Patch?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 215 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.