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 skills add cloudbees-oss/devops-agent-kit --skill security-scangit clone --depth 1 https://github.com/cloudbees-oss/devops-agent-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/security-scan)<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/security-scan"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/security-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cloudbees-oss/devops-agent-kit/security-scan"><img src="https://agentmods.dev/badge/skills/cloudbees-oss/devops-agent-kit/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00025 | $0.00589 |
| Opus 5.5 | $0.00010 | $0.00236 |
| Sonnet 5.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 1mo ago.
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.
- 1mo ago 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 (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 589 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…