Borrowing it
Nothing to install: this file belongs to mazumba/opencode-dockerized. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mazumba/opencode-dockerized/main/.opencode/config/skills/patch-cve/SKILL.mdgit clone --depth 1 https://github.com/mazumba/opencode-dockerizedWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mazumba/opencode-dockerized/patch-cve)<a href="https://agentmods.dev/skills/mazumba/opencode-dockerized/patch-cve"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/patch-cve/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mazumba/opencode-dockerized/patch-cve"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/patch-cve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00061 | $0.01127 |
| Opus 5.5 | $0.00024 | $0.00451 |
| Sonnet 5.5 | $0.00012 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
patch-cve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 24d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patch CVE
Triage and remediate each CVE ID the user supplies, in sequence. Every CVE ends in exactly one outcome: fixed, suppressed with justification, or already suppressed. Each fix path proposes a change and waits for approval before writing anything.
1. Check .trivyignore
Look for the CVE ID in .trivyignore in the project root.
- Present and the
exp:date has not passed today: report it as already suppressed and move on. - Present and the
exp:date has passed: re-triage from scratch. - Absent: proceed.
2. Fetch CVE details
Always fetch https://nvd.nist.gov/vuln/detail/<CVE-ID>.
If a Dockerfile exists, read its FROM line to determine the base distro and also check that distro's security tracker:
| Distro | Tracker |
|---|---|
| Debian / Ubuntu | https://security-tracker.debian.org/tracker/<CVE-ID> |
| Alpine | https://security.alpinelinux.org/vuln/<CVE-ID> |
| Red Hat / UBI / CentOS | https://access.redhat.com/security/cve/<CVE-ID> |
| Other | the distro's own security advisory database |
Extract:
- Description and CWE
- Affected package and vulnerable version range
- Fixed version, if any
- Attack vector and the conditions required to exploit it
3. Read AGENTS.md
If AGENTS.md exists in the project root, read it before choosing a fix path. It supplies the stack and package manager, the quality gate to run after a fix, and project context for the reachability assessment.
4. Choose the fix path
Pick the single path that applies. When several match, disambiguate with AGENTS.md.
A. Node/JS package
The affected package appears in bun.lock, package-lock.json, yarn.lock or pnpm-lock.yaml, and the locked version lies within the vulnerable range.
Propose the manifest change for the package manager in use:
- bun, npm, pnpm:
"overrides": { "<package>": "<fixed-version>" }inpackage.json - yarn:
"resolutions": { "<package>": "<fixed-version>" }inpackage.json
After approval:
- Apply the manifest change.
- Run the install command in the environment
AGENTS.mddescribes (for examplebun install,npm install). - Verify the lockfile no longer contains the vulnerable version.
- Run the quality gate from
AGENTS.md.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 24d ago First seen · 104 lines · 61 tokens per session scan A f9ac2c9d817f
patch-cve is a skill published in the GitHub repository mazumba/opencode-dockerized (6 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 1,127 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
k8s-networking
Kubernetes networking management for services, ingresses, endpoints, and network policies. Use when configuring connectivity, load balancing, or network isolation.