skill-cloudbees-oss-devops-agent-kit-security-scan · by Install
$ agentstack add skill-cloudbees-oss-devops-agent-kit-security-scan ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cloudbees-oss-devops-agent-kit-security-scan) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Security Scan: $ARGUMENTS
If "all" or no argument:
security_issues_all_get— get all open security issues across the orgcomponents_list— get all components for cross-referencing- For each component with findings:
a. branches_list — find the default branch b. security_findings_summary_get — severity breakdown c. security_issues_open_get — detailed finding list d. runs_list(limit=3) — check if recent scans ran successfully
- Get org-level security reports:
a. organizations_suborg_report(s1) — components with scanner coverage b. organizations_suborg_report(s2) — workflows with scanner coverage c. organizations_suborg_report(s6) — scan types in automations d. organizations_suborg_report(s8) — SLA status NOTE: s4 and s5 may return "No Data Found" at the org level. Use component-level tools instead if this happens.
- Present a security dashboard:
Organization Security Posture
| Component | Critical | High | Medium | Low | Scanner | SLA Status | |-----------|----------|------|--------|-----|---------|------------| | name | N | N | N | N | type | On track |
Scanner coverage: N of M components (X%) Workflow coverage: N of M workflows (X%) Scan types active: SAST / DAST / SCA / Container
- For each finding, include: finding type, file path, line number, SLA due date
- Rank findings by priority: Critical > High with approaching SLA > High > Medium > Low
- Provide remediation recommendations
If specific component:
components_search— find the componentbranches_list— find branchessecurity_findings_summary_get— severity breakdown for default branchsecurity_issues_open_get— all open issues with detailsruns_list(limit=5)— recent scan run history
- Present component-level security report with:
- Finding details (type, file, line, severity, SLA)
- Scan history (when last scanned, scan frequency)
- Remediation steps specific to each finding type
- Offer next actions:
- "/file-ticket security [finding]" for high-priority findings
- Post security summary to Slack
- Check if a fix branch exists in GitHub
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cloudbees-oss
- Source: cloudbees-oss/devops-agent-kit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.