Deepsec Documentation Guide
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.
$ npx skills add rundeck/rundeck --skill cve-remediation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rundeck/rundeck cve-remediation --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/rundeck/rundeck.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cve-remediation .claude/skills/cve-remediation && 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 "cve-remediation" agent skill from https://github.com/rundeck/rundeck/tree/main/.claude/skills/cve-remediation into .claude/skills/cve-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-remediation", 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/rundeck/rundeck/tree/main/.claude/skills/cve-remediationType 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 rundeck/rundeck --skill cve-remediation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rundeck/rundeck cve-remediation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rundeck/rundeck.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/cve-remediation .agents/skills/cve-remediation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cve-remediation" agent skill from https://github.com/rundeck/rundeck/tree/main/.claude/skills/cve-remediation into .agents/skills/cve-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-remediation", 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 rundeck/rundeck --skill cve-remediation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rundeck/rundeck cve-remediation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rundeck/rundeck.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/cve-remediation .cursor/skills/cve-remediation && 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 "cve-remediation" agent skill from https://github.com/rundeck/rundeck/tree/main/.claude/skills/cve-remediation into .cursor/skills/cve-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-remediation", 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/rundeck/rundeck.git --path .claude/skills/cve-remediation--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 rundeck/rundeck --skill cve-remediation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rundeck/rundeck cve-remediation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rundeck/rundeck.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/cve-remediation .gemini/skills/cve-remediation && 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 "cve-remediation" agent skill from https://github.com/rundeck/rundeck/tree/main/.claude/skills/cve-remediation into .gemini/skills/cve-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-remediation", 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 rundeck/rundeck cve-remediationInstalls 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 rundeck/rundeck --skill cve-remediation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rundeck/rundeck.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/cve-remediation .github/skills/cve-remediation && 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 "cve-remediation" agent skill from https://github.com/rundeck/rundeck/tree/main/.claude/skills/cve-remediation into .github/skills/cve-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-remediation", 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 rundeck/rundeck --skill cve-remediation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rundeck/rundeck cve-remediation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rundeck/rundeck.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/cve-remediation .opencode/skills/cve-remediation && 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 "cve-remediation" agent skill from https://github.com/rundeck/rundeck/tree/main/.claude/skills/cve-remediation into .opencode/skills/cve-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-remediation", 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.
cve-remediationVerify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.
Cve Remediation is an agent skill from rundeck/rundeck. Verify if a CVE affects the project and remediate it. Checks dependencies, identifies vulnerable versions, suggests/applies fixes, and validates changes. Use when analyzing security vulnerabilities or responding to CVE reports.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Vulnerability scanning. The repository describes itself as: Enable Self-Service Operations: Give specific users access to your existing tools, services, and scripts. The licence is Apache-2.0.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a83e3ca. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmrggitcurljqghFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
nvd.nist.govcve.circl.luservices.nvd.nist.govFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cve Remediation loads about 2.9k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 575 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.
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); files beside SKILL.md are not scanned.
The full file from rundeck/rundeck at commit a83e3ca, republished under its Apache-2.0 licence (© rundeck). 575 words, ~2,938 tokens.
.claude/skills/cve-remediation/SKILL.md (or your agent's skills folder).Systematic process for verifying and remediating CVE (Common Vulnerabilities and Exposures) impacts on Rundeck.
1. CVE Analysis → 2. Dependency Check → 3. Impact Assessment → 4. Fix Strategy → 5. Implementation → 6. Validation → 7. DocumentationCVE-2024-1234# Quick CVE lookup
curl -s "https://cve.circl.lu/api/cve/${CVE_ID}" | jq
# Or use NVD API
curl -s "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=${CVE_ID}"What to extract:
Check these files for dependency definitions:
# Root dependencies
cat gradle.properties
# All build files
find . -name "build.gradle" -not -path "*/node_modules/*"
# Frontend dependencies
cat rundeckapp/grails-spa/packages/ui-trellis/package.jsonUse Grep to find the dependency across the codebase:
# Example: Search for log4j versions
rg "log4j" gradle.properties build.gradle
rg "log4jVersion" --type gradle
# Example: Search for jackson versions
rg "jackson" gradle.properties# Generate dependency tree
./gradlew dependencies > dependency-tree.txt
# Search for vulnerable library in tree
grep -i "vulnerable-library" dependency-tree.txt
# Check specific module
./gradlew :module-name:dependencies# Check npm dependencies
cd rundeckapp/grails-spa/packages/ui-trellis
npm list <vulnerable-package>
# Check for vulnerabilities
npm audit
npm audit --json | jq '.vulnerabilities'Critical Impact:
Medium Impact:
Low Impact:
Create a summary:
## CVE Impact Assessment: ${CVE_ID}
**Affected Component:** [library name and version]
**Current Version:** [version in project]
**Vulnerable Versions:** [range from CVE]
**Fixed Version:** [recommended upgrade]
**Severity:** [Critical/High/Medium/Low]
**Impact on Rundeck:** [Direct/Transitive/Not Affected]
**Usage in Project:**
- Location: [file paths]
- Modules affected: [list]
- Production impact: [Yes/No - explain]
**Exploitability:**
- Attack vector: [Local/Network/Adjacent]
- Requires: [Authentication/User interaction/etc]
- Impact on us: [likely/unlikely - explain]When to use:
Steps:
gradle.properties or build.gradleWhen to use:
Steps:
When to use:
Options:
When to use:
Requirements:
Even for dependency upgrades, write a test first:
// Example: Test that vulnerable version is NOT present
def "should not use vulnerable log4j version"() {
when:
def dependencies = project.configurations.runtimeClasspath.resolvedConfiguration.resolvedArtifacts
then:
!dependencies.any { it.name == 'log4j-core' && it.moduleVersion.id.version.startsWith('2.14') }
}For gradle.properties:
# Before
log4jVersion=2.14.1
# After (with comment explaining why)
# Updated from 2.14.1 to fix CVE-2021-44228 (Log4Shell)
log4jVersion=2.17.1For build.gradle:
// Exclude vulnerable transitive dependency
dependencies {
implementation('some-library:1.0') {
exclude group: 'vulnerable-lib', module: 'vulnerable-module'
}
// Add fixed version explicitly
implementation 'vulnerable-lib:vulnerable-module:fixed-version'
}For package.json:
{
"dependencies": {
"vulnerable-package": "^fixed.version"
},
"overrides": {
"transitive-vulnerable": "^fixed.version"
}
}# Format code
./gradlew spotlessApply
# Quick compilation check
./gradlew compileGroovy compileJava# Check gradle dependencies
./gradlew dependencies | grep -i "vulnerable-library"
# Check npm dependencies
npm list vulnerable-package
# Verify version in build output
./gradlew build --info | grep "vulnerable-library"# Full test suite (REQUIRED)
./gradlew test
# Specific module tests
./gradlew :affected-module:test
# Frontend tests
CORE_UI=rundeckapp/grails-spa/packages/ui-trellis
npm run --prefix "$CORE_UI" ci:test:unit# API functional tests
./gradlew :functional-test:apiTest
# Selenium tests (if UI affected)
./gradlew :functional-test:seleniumTest# Full build
./gradlew build
# Start application locally
./gradlew bootRun
# Manual smoke test checklist:
# - Application starts without errors
# - Login works
# - Core functionality works
# - No new warnings/errors in logs# Re-run security scanner
./gradlew dependencyCheckAnalyze
# Check for CVE in updated dependencies
./gradlew dependencies | grep -i "CVE"
# Frontend audit
npm audit
npm audit fix --dry-runIf not already created:
Title: Fix CVE-XXXX-XXXX in [library]
Labels: security
Body:
CVE: CVE-XXXX-XXXX
Affected: [library] version [X.X.X]
Severity: [CVSS score and rating]
Fix: Upgrade to version [Y.Y.Y]
Impact: [Description of impact on Rundeck]
Links:
- NVD: https://nvd.nist.gov/vuln/detail/CVE-XXXX-XXXX
- Vendor advisory: [link]Fix CVE-XXXX-XXXX in [library]
Upgrade [library] from [old-version] to [new-version] to address
security vulnerability CVE-XXXX-XXXX.
Vulnerability Details:
- Severity: [Critical/High/Medium/Low]
- CVSS: [score]
- Impact: [brief description]
Changes:
- Updated [library]Version in gradle.properties
- Ran full test suite - all passing
- Verified no functional regressionsgh pr create --title "Fix CVE-XXXX-XXXX in [library]" --body "..."PR Description (in addition to template):
## Security Fix
**CVE:** CVE-XXXX-XXXX
**Severity:** [Critical/High/Medium/Low] (CVSS [score])
**Affected:** [library] [version-range]
**Fix:** Upgrade to [new-version]
**Impact Assessment:**
- [X] Direct dependency / [ ] Transitive dependency
- [X] Production code / [ ] Test code only
- Exploitable: [Yes/No - explanation]
**Testing:**
- [X] All unit tests pass
- [X] All functional tests pass
- [X] Manual smoke test completed
- [X] Security scan shows CVE resolved
**References:**
- NVD: https://nvd.nist.gov/vuln/detail/CVE-XXXX-XXXX
- Vendor advisory: [link]If the project has a security changelog or vulnerability log, update it:
## [Date] - CVE-XXXX-XXXX
**Fixed in:** Version X.Y.Z
**CVE:** CVE-XXXX-XXXX
**Severity:** [level]
**Component:** [library] [old-version] → [new-version]
**Impact:** [description]
**Credit:** [who reported it]1. Search for dependency in gradle.properties
2. Update version
3. Run ./gradlew dependencies to verify
4. Run ./gradlew test
5. Create PR1. Find which direct dependency pulls it in
2. Add explicit dependency with fixed version
3. Or exclude vulnerable transitive and add fixed version
4. Verify with ./gradlew dependencies
5. Run tests and create PR1. cd to package directory
2. Run npm audit
3. Update package.json or use overrides
4. Run npm test
5. Commit and create PR1. Document the issue in a GitHub issue
2. Assess actual risk/exploitability
3. Implement workarounds if needed
4. Set up monitoring/alerts
5. Schedule re-assessment when fix availableUse this checklist for every CVE remediation:
./gradlew spotlessApply)./gradlew compileGroovy compileJava)./gradlew test)# Find dependency in project
rg "library-name" gradle.properties build.gradle
# Check dependency tree
./gradlew dependencies | grep "library-name"
# Update and verify
vim gradle.properties # Update version
./gradlew spotlessApply
./gradlew compileGroovy compileJava
./gradlew test
# Security checks
./gradlew dependencyCheckAnalyze
npm audit
# Create PR
git checkout -b fix-cve-xxxx-xxxx
git add gradle.properties
git commit -m "Fix CVE-XXXX in library"
gh pr create --web.claude/docs/testing-guidelines.md.claude/docs/build-commands.md© rundeck, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/cve-remediation of rundeck/rundeck.
Open the folder on GitHubat commit a83e3ca
Cve Remediation 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 |
|---|---|---|---|---|---|---|
| Cve Remediation this skillrundeck/rundeck | 6.3k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Deepsec Documentation Guidevercel-labs/deepsec | 8.1k | — | ~956 | Automated safety check: Pass | Apache-2.0 | |
| Shiro Attack CLISummerSec/ShiroAttack2 | 2.6k | — | ~945 | Automated safety check: Pass | MIT | |
| Native Dependency Updatemono/SkiaSharp | 5.6k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Forensifyalexgreensh/repo-forensics | 190 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| Write Cve Ruleevdenis/cvehound | 138 | — | ~2.5k | Automated safety check: Pass | GPL-3.0 |
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
mono/SkiaSharp
Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.
alexgreensh/repo-forensics
Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.
evdenis/cvehound
Write, debug, or validate a CVEhound detection rule (.cocci or .grep) for a Linux kernel CVE.
TheDecipherist/claude-code-mastery
Checks a codebase for hardcoded secrets, vulnerable dependencies, weak input handling, weak authentication and unsafe transport settings before deployment or merge.
rundeck/rundeck
Backport commits from an existing GitHub Pull Request to a target branch and open a new backport PR.
rundeck/rundeck
Generate standardized CONTEXT.md files for features. An agent skill from rundeck/rundeck.
rundeck/rundeck
Internationalize Vue component templates by replacing all hardcoded strings with $t() calls and adding translations to i18n.ts or enUS.js.
rundeck/rundeck
Guide a new contributor through the rundeck OSS repo. An agent skill from rundeck/rundeck.
rundeck/rundeck
Write Vue component unit tests. An agent skill from rundeck/rundeck.
rundeck/rundeck
Create REST API endpoints with proper OpenAPI annotations, API versioning, and testing following Rundeck standards.
Categories
Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck. Cve Remediation is an agent skill from rundeck/rundeck. Verify if a CVE affects the project and remediate it.
Cve Remediation fits situations like: analyzing security vulnerabilities; responding to CVE reports.
Run `npx skills add rundeck/rundeck --skill cve-remediation -a claude-code`. Or copy the skill folder (.claude/skills/cve-remediation in rundeck/rundeck) into .claude/skills/cve-remediation in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rundeck/rundeck --skill cve-remediation -a codex`. Or copy the skill folder (.claude/skills/cve-remediation in rundeck/rundeck) into .agents/skills/cve-remediation in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rundeck/rundeck --skill cve-remediation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cve-remediation, .gemini/skills/cve-remediation, .github/skills/cve-remediation and .opencode/skills/cve-remediation in your project.
Going by SKILL.md and its folder, Cve Remediation needs the command-line tools its instructions call (npm, rg, git, curl, jq and gh).
SKILL.md names 3 domains. In commands or code: nvd.nist.gov, cve.circl.lu and services.nvd.nist.gov; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
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. Review the folder before installing.
Cve Remediation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cve Remediation: Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Shiro Attack CLI (SummerSec/ShiroAttack2, 2.6k stars), Native Dependency Update (mono/SkiaSharp, 5.6k stars) and Forensify (alexgreensh/repo-forensics, 190 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rundeck (a GitHub organization) maintains it in rundeck/rundeck, which has 6,330 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.
Source: rundeck/rundeck on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.