jenkins-cicd

jenkins-cicd is a skill for Claude Code, Codex from automateyournetwork/netclaw. It costs 31 tokens per session (3,262 once invoked), scanned A, original, Apache-2.0.

A Jenkins integration for managing CI/CD pipelines used in network-automation projects. CI/CD means automatically building, testing, and delivering changes through a pipeline.

In plain words
What is it for?
Use it to list jobs, monitor builds, trigger approved pipelines with parameters, inspect build logs, and track changes from source control.
Why use it?
It brings build status, logs, queued jobs, and source-control changes together so failed or delayed automation runs are easier to investigate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to list jobs, monitor builds, trigger approved pipelines with parameters, inspect build logs, and track changes from source control.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/automateyournetwork/netclaw/jenkins-cicd
Install

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.

Any agent
npx skills add automateyournetwork/netclaw --skill jenkins-cicd
Clone the repo
git clone --depth 1 https://github.com/automateyournetwork/netclaw

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for jenkins-cicd

README.md
[![agentmods](https://agentmods.dev/badge/skills/automateyournetwork/netclaw/jenkins-cicd/github.svg)](https://agentmods.dev/skills/automateyournetwork/netclaw/jenkins-cicd)
Your own site
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/jenkins-cicd"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/jenkins-cicd/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.

agentmods 80×15 button for jenkins-cicd

Your own site · 80×15
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/jenkins-cicd"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/jenkins-cicd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.03262
Opus 5 $0.00015 $0.01631
Sonnet 5 $0.00006 $0.00652
Haiku 4.5 $0.00003 $0.00326

Measured 8d ago against content hash 20210beba015, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

jenkins-cicd 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 8d 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.

workspace/skills/jenkins-cicd/SKILL.md · 369 lines

How it starts

The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Jenkins CI/CD Skill

Purpose

Manage Jenkins CI/CD pipelines for network automation workflows. This skill provides operational workflows for monitoring job and build status, triggering builds with parameters, analyzing build logs for troubleshooting, and tracking SCM changes across Jenkins projects.

The Jenkins MCP server is an official Jenkins plugin running natively inside Jenkins via Streamable HTTP transport — netclaw connects to it as a remote HTTP client.

Golden Rule

Never trigger a build or modify build metadata without explicit operator confirmation. All write operations (triggerBuild, updateBuild) require human-in-the-loop approval per Constitution XIV. Always read current state before proposing any write action (Constitution II — Read-Before-Write).


Workflow 1: Pipeline and Build Monitoring (US1 — MVP)

Monitor Jenkins job status, build results, queue state, and pipeline run history.

Steps

  1. List all jobs — Use getJobs with optional pagination (offset, limit) and regex name filter to discover available jobs.

    Tool: getJobs
    Parameters: { "nameFilter": "deploy-.*", "offset": 0, "limit": 25 }
    
  2. Get job details — Use getJob with the full job name (supports folder paths like folder1/folder2/job-name) to retrieve job configuration, last build number, and health status.

    Tool: getJob
    Parameters: { "fullName": "network-automation/deploy-network-config" }
    
  3. Get build details — Use getBuild with job name and build number to retrieve result, duration, timestamp, parameters, and causes.

    Tool: getBuild
    Parameters: { "jobFullName": "deploy-network-config", "buildNumber": 42 }
    
  4. Check queue status — Use getQueueItem to inspect queued build requests — waiting reason, position, estimated start time.

    Tool: getQueueItem
    Parameters: { "queueId": 1234 }
    
  5. View pipeline run history — Use getPipelineRuns to list pipeline execution history with status, duration, and branch info.

    Tool: getPipelineRuns
    Parameters: { "jobFullName": "deploy-network-config" }
    

Read the full file on GitHub · 369 lines

Changes

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.

  1. 8d ago First seen · 369 lines · 31 tokens per session scan A 20210beba015

Subscribe to this mod's changes

jenkins-cicd is a skill published in the GitHub repository automateyournetwork/netclaw (655 stars, last pushed 5d ago), licensed Apache-2.0. It adds 31 tokens to every session and 3,262 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

CI/CD Pipeline Advanced

Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.

PramodDutta/qaskills · 45 tokens

cicd-expert

Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.

personamanagmentlayer/pcl · 67 tokens

CI/CD Pipeline Config

CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.

PramodDutta/qaskills · 35 tokens

cicd-pipeline-builder

Generate CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins with best practices.

glincker/claude-code-marketplace · 24 tokens

integrating-sast-into-github-actions-pipeline

This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and…

xalgorix/xalgorix · 84 tokens

scanning-containers-with-trivy-in-cicd

This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…

xalgorix/xalgorix · 74 tokens