Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/mazumba/opencode-dockerized/patch-cvegit clone --depth 1 https://github.com/mazumba/opencode-dockerizedWhat 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 | $0.00026 | $0.01315 |
| Opus 5 | $0.00013 | $0.00658 |
| Sonnet 5 | $0.00005 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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 yesterday.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage and remediate each CVE ID passed in $ARGUMENTS. Multiple CVEs may be space-separated.
Invocation
/patch-cve CVE-2026-42570
/patch-cve CVE-2026-42570 CVE-2026-48962 CVE-2026-9538
Steps
Process each CVE ID in sequence.
1. Check .trivyignore
Look for the CVE ID in .trivyignore in the project root.
- If present and the
exp:date has not passed today → skip this CVE, report it as already suppressed. - If present and the
exp:date has passed → re-triage it from scratch. - If absent → proceed.
2. Fetch CVE details
Always fetch from NVD (https://nvd.nist.gov/vuln/detail/<CVE-ID>) for general CVE details.
If a Dockerfile exists in the project, inspect the FROM line to determine the base distro, then additionally check the appropriate distro security 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 distros → search for the distro's own security advisory database
If no Dockerfile exists, NVD alone is sufficient.
Extract:
- Description and CWE
- Affected package name and installed version range
- Fixed version (if any)
- Attack vector and prerequisites (what conditions are required to exploit it)
3. Read AGENTS.md
If an AGENTS.md exists in the project root, read it before proceeding. Use it to:
- Understand the project stack and package manager
- Understand the quality gate protocol to follow after applying a fix
- Understand any project-specific context relevant to reachability assessment
4. Detect ecosystem and fix path
Determine which of the following applies. Use AGENTS.md context to disambiguate when multiple match.
A — Node/JS package
The affected package appears in one of: bun.lock, package-lock.json, yarn.lock, pnpm-lock.yaml.
Check whether the installed version in the lockfile is within the vulnerable range and whether a fixed version exists.
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.
- yesterday First seen · 122 lines · 26 tokens per session scan A 24347e85d10f
patch-cve is a command published in the GitHub repository mazumba/opencode-dockerized (5 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 1,315 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.