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 skills/cloudbees-oss/devops-agent-kit/security-scannpx skills add cloudbees-oss/devops-agent-kit --skill security-scangit clone --depth 1 https://github.com/cloudbees-oss/devops-agent-kitWhat 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.00025 | $0.00589 |
| Opus 5 | $0.00013 | $0.00295 |
| Sonnet 5 | $0.00005 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
security-scan 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan: $ARGUMENTS
If "all" or no argument:
-
security_issues_all_get— get all open security issues across the org -
components_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 component -
branches_list— find branches -
security_findings_summary_get— severity breakdown for default branch -
security_issues_open_get— all open issues with details -
runs_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
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 · 62 lines · 25 tokens per session scan A 98edd123e017
security-scan is a skill published in the GitHub repository cloudbees-oss/devops-agent-kit (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 589 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…