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 automateyournetwork/netclaw --skill jenkins-cicdgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/jenkins-cicd)<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.
<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>- NVIDIA SkillSpector pass
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.00031 | $0.03262 |
| Opus 5 | $0.00015 | $0.01631 |
| Sonnet 5 | $0.00006 | $0.00652 |
| Haiku 4.5 | $0.00003 | $0.00326 |
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.
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
-
List all jobs — Use
getJobswith optional pagination (offset,limit) and regex name filter to discover available jobs.Tool: getJobs Parameters: { "nameFilter": "deploy-.*", "offset": 0, "limit": 25 } -
Get job details — Use
getJobwith the full job name (supports folder paths likefolder1/folder2/job-name) to retrieve job configuration, last build number, and health status.Tool: getJob Parameters: { "fullName": "network-automation/deploy-network-config" } -
Get build details — Use
getBuildwith job name and build number to retrieve result, duration, timestamp, parameters, and causes.Tool: getBuild Parameters: { "jobFullName": "deploy-network-config", "buildNumber": 42 } -
Check queue status — Use
getQueueItemto inspect queued build requests — waiting reason, position, estimated start time.Tool: getQueueItem Parameters: { "queueId": 1234 } -
View pipeline run history — Use
getPipelineRunsto list pipeline execution history with status, duration, and branch info.Tool: getPipelineRuns Parameters: { "jobFullName": "deploy-network-config" }
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.
- 8d ago First seen · 369 lines · 31 tokens per session scan A 20210beba015
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.
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.
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.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.
cicd-pipeline-builder
Generate CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins with best practices.
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…
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…