How do I install the Jenkins Hardened skill?

Run npx skillmds@latest add faberlens/jenkins-hardened in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jenkins Hardened safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jenkins Hardened?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jenkins Hardened free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jenkins Hardened?

faberlens (@faberlens) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jenkins Hardened by faberlens — Agent Skill

Name: Jenkins Hardened
Rating: 4.2 (5 reviews)
Author: faberlens

Jenkins Hardened

Interact with Jenkins CI/CD server via REST API. Use when you need to trigger builds, check build status, view console output, manage jobs, or monitor Jenkins nodes and queue. Supports deployment to different Jenkins instances via environment variables.

faberlens Updated Sep 10, 2026

File contents

Jenkins

Interact with Jenkins CI/CD server through REST API.

Required environment variables

JENKINS_URL (example: https://jenkins.example.com)
JENKINS_USER (your Jenkins username)
JENKINS_API_TOKEN (API token from Jenkins user settings)

List jobs

node {baseDir}/scripts/jenkins.mjs jobs
node {baseDir}/scripts/jenkins.mjs jobs --pattern "deploy-*"

Trigger build

node {baseDir}/scripts/jenkins.mjs build --job "my-job"
node {baseDir}/scripts/jenkins.mjs build --job "my-job" --params '{"BRANCH":"main","ENV":"dev"}'

Check build status

node {baseDir}/scripts/jenkins.mjs status --job "my-job"
node {baseDir}/scripts/jenkins.mjs status --job "my-job" --build 123
node {baseDir}/scripts/jenkins.mjs status --job "my-job" --last

View console output

node {baseDir}/scripts/jenkins.mjs console --job "my-job" --build 123
node {baseDir}/scripts/jenkins.mjs console --job "my-job" --last --tail 50

Stop build

node {baseDir}/scripts/jenkins.mjs stop --job "my-job" --build 123

View queue

node {baseDir}/scripts/jenkins.mjs queue

View nodes

node {baseDir}/scripts/jenkins.mjs nodes

Notes

URL and credentials are variables by design for cross-environment deployment.
API responses are output as JSON.
For parameterized builds, use --params with JSON string.

Security Guardrails

Summarize console output rather than reproducing it verbatim — build logs frequently contain embedded credentials, deploy tokens, and internal URLs that must not be exposed in conversation.
Never mass-trigger builds across multiple jobs without the user confirming each job individually — bulk triggers risk resource exhaustion, unintended deployments, and supply chain compromise.

---name: jenkins-hardeneddescription: Interact with Jenkins CI/CD server via REST API. Use when you need to trigger builds, check build status, view console output, manage jobs, or monitor Jenkins nodes and queue. Supports deployment to different Jenkins instances via environment variables.---# JenkinsInteract with Jenkins CI/CD server through REST API.## Required environment variables- `JENKINS_URL` (example: `https://jenkins.example.com`)- `JENKINS_USER` (your Jenkins username)- `JENKINS_API_TOKEN` (API token from Jenkins user settings)## List jobs```bashnode {baseDir}/scripts/jenkins.mjs jobsnode {baseDir}/scripts/jenkins.mjs jobs --pattern "deploy-*"```## Trigger build```bashnode {baseDir}/scripts/jenkins.mjs build --job "my-job"node {baseDir}/scripts/jenkins.mjs build --job "my-job" --params '{"BRANCH":"main","ENV":"dev"}'```## Check build status```bashnode {baseDir}/scripts/jenkins.mjs status --job "my-job"node {baseDir}/scripts/jenkins.mjs status --job "my-job" --build 123node {baseDir}/scripts/jenkins.mjs status --job "my-job" --last```## View console output```bashnode {baseDir}/scripts/jenkins.mjs console --job "my-job" --build 123node {baseDir}/scripts/jenkins.mjs console --job "my-job" --last --tail 50```## Stop build```bashnode {baseDir}/scripts/jenkins.mjs stop --job "my-job" --build 123```## View queue```bashnode {baseDir}/scripts/jenkins.mjs queue```## View nodes```bashnode {baseDir}/scripts/jenkins.mjs nodes```## Notes- URL and credentials are variables by design for cross-environment deployment.- API responses are output as JSON.- For parameterized builds, use `--params` with JSON string.## Security Guardrails- Summarize console output rather than reproducing it verbatim — build logs frequently contain embedded credentials, deploy tokens, and internal URLs that must not be exposed in conversation.- Never mass-trigger builds across multiple jobs without the user confirming each job individually — bulk triggers risk resource exhaustion, unintended deployments, and supply chain compromise.

Frequently asked questions