How to Use CISA KEV recent additions in opencode
Get vulnerabilities recently added to CISA's catalog, with affected products, required actions, ransomware status, and due dates. Use it for daily triage or weekly briefings; the date describes catalog inclusion, not discovery.
Prompts to try with CISA KEV recent additions in opencode
Copy an example into opencode, or ask in your own words.
Use CISA KEV recent additions for the past seven days, compare affected products with the repository's software inventory, and create a Markdown triage report with matching CVEs and required actions.
Use CISA KEV recent additions to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from CISA KEV recent additions and tell me what changed since last week.
Check CISA KEV recent additions and summarize what you find in three bullet points.
Pull the newest data from CISA KEV recent additions and give me the result as a table.
How to set up CISA KEV recent additions in opencode
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
Leave out --global to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
- Sign in
Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, /mcps starts the same sign-in.
opencode mcp auth spiral
- Check it
Spiral shows as connected.
opencode mcp list
Use the Spiral skill
- Send opencode this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run CISA KEV recent additions
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "cisa-gov/vulnerabilities/kev_recent", "input": { "days": 7 } }'
Then paste one of the prompts above: opencode finds CISA KEV recent additions on Spiral, shows the price and runs it.
CISA KEV recent additions providers and prices
Spiral runs CISA KEV recent additions through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask opencode for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Days | 1 to 90 | 7 | Window length in days, ending today on CISA's US Eastern calendar; 1 means added today. CISA adds entries most weekdays, not every day. |
| Page size | 1 to 100 | 100 | page_size |
Every API field of CISA Known Exploited Vulnerabilities (KEV) catalog · Kev recent is on its tool page: open its card above.
What can you do with CISA KEV recent additions in opencode?
Turn CISA KEV records into patch ticket drafts tied to the project's scanner findings or dependency inventory. A coding agent can match CVE IDs, attach CISA's required actions, and organize relevant records by due date.
Prioritize scanner findings
Match scanner CVEs against CISA records and put confirmed KEV matches into a remediation review with the required actions and due dates.
Prepare patch tickets
Turn relevant catalog records into ticket drafts containing the CVE, affected product, vulnerability description, required action, and supporting references.
Review ransomware exposure
Identify records marked as known ransomware use within a CVE list, recent additions, or a vendor review, then compare affected products with the organization's inventory.
Plan remediation work
Arrange relevant KEV records by due date and required action to prepare a patch planning meeting.
Write technology-specific security briefings
Summarize exploited vulnerabilities affecting technologies such as Microsoft Exchange, Ivanti Connect Secure, or Apache Log4j, with descriptions and remediation references.
Review recurring software weaknesses
Organize relevant KEV records by their reported CWE codes to support an engineering discussion about recurring weakness types.
Prepare a vendor remediation review
Collect relevant records for a software supplier and use CISA's required actions and linked references to prepare specific questions about remediation.
More on CISA KEV recent additions and opencode
Overview
CISA KEV recent additions in other agents
Questions about CISA KEV recent additions in opencode
Can opencode use CISA KEV recent additions?
Yes. Add Spiral to opencode as an MCP server, and opencode can find and run CISA KEV recent additions like any built-in tool.
How much does CISA KEV recent additions cost in opencode?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your opencode plan is separate.
Do I need an Alexandria account to use CISA KEV recent additions in opencode?
No. Spiral runs CISA KEV recent additions on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up CISA KEV recent additions in opencode?
About two minutes: add the server, then sign in, then check it.
Does opencode wait while CISA KEV recent additions runs?
CISA KEV recent additions runs in the background. opencode starts the run, checks on it and gives you the json when it's ready.
Does CISA KEV contain every disclosed vulnerability?
No. CISA requires reliable evidence of exploitation in the wild and a clear remediation action before inclusion, so KEV covers a narrower set of vulnerabilities.
How often does CISA update the catalog?
Updates typically happen on weekdays during normal US Eastern business hours when CISA has new or updated entries. That is a typical publishing pattern, not a fixed daily release.
Does the date added show when exploitation began?
No. It records when CISA added the vulnerability to KEV, so a recent addition does not establish a recent discovery or first attack.
Does Unknown ransomware status mean no ransomware use?
No. CISA defines Unknown as lacking confirmation that the vulnerability has been used for ransomware.
Can I see how an existing KEV record changed?
The catalog file has no accessible inline revision log. CISA's public GitHub repository preserves commit history that can help identify changes to existing entries.
Start using CISA KEV recent additions in opencode
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into opencode:
set up https://spiral.ai/SKILL.md


