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/abdullahkhawer/devops-skills/jenkins-clinpx skills add abdullahkhawer/devops-skills --skill jenkins-cligit clone --depth 1 https://github.com/abdullahkhawer/devops-skillsWrote 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/abdullahkhawer/devops-skills/jenkins-cli)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/jenkins-cli"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/jenkins-cli.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.01752 |
| Opus 5 | $0.00006 | $0.00876 |
| Sonnet 5 | $0.00003 | $0.00350 |
| Haiku 4.5 | $0.00001 | $0.00175 |
Grade A, and why
jenkins-cli scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Always use `jenkins-cli.jar` for all Jenkins operations. Do **not** use `curl` or other HTTP clients against the Jenkins REST API. How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jenkins CLI Skill
Use the CLI setup and command format below when constructing all jenkins-cli commands.
Instances
Update the table below with your Jenkins server URLs and auth file paths:
| Environment | Server URL | Auth File |
|---|---|---|
| Production | https://<your-jenkins-prod-url> |
jenkins-cli/prod.auth |
| Staging | https://<your-jenkins-staging-url> |
jenkins-cli/staging.auth |
If the target server is unclear, ask the user before running any command.
CLI Setup
- JAR File:
jenkins-cli/jenkins-cli.jar(working directory's root) - Auth Files: one per server — see instance table above. File contents format:
username:api-token
All commands must be run from the working directory's root (where jenkins-cli/ directory exists).
Prerequisites (one-time setup by user)
If the jenkins-cli/ directory does not exist yet, or jenkins-cli.jar or the auth file for the target server is missing, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself.
- Create the directory
jenkins-cliin the working directory's root. - Download the JAR from
<YOUR_JENKINS_URL>/jnlpJars/jenkins-cli.jarand save it asjenkins-cli/jenkins-cli.jar. - Create an auth file for each server you intend to use, with your credentials in this exact format:
username:api-tokenjenkins-cli/prod.authjenkins-cli/staging.auth
Command Format
java -jar jenkins-cli/jenkins-cli.jar -s <SERVER_URL> -auth @<AUTH_FILE> [command]
Example (production):
java -jar jenkins-cli/jenkins-cli.jar -s https://<your-jenkins-prod-url> -auth @jenkins-cli/prod.auth who-am-i
Available Commands
Read-only (safe, no confirmation needed)
| Command | Description |
|---|---|
who-am-i |
Verify auth and show permissions |
version |
Show Jenkins version |
list-jobs [folder] |
List all jobs (optionally in a folder/view) |
get-job <job> |
Dump job config XML to stdout |
console <job> [build#] |
Get console output of a build; build# accepts integers or Jenkins specifiers like lastSuccessfulBuild, lastBuild, lastFailedBuild |
list-changes <job> [build#] |
Show changelog for a build; build# must be an integer — specifiers like lastSuccessfulBuild are not accepted |
get-node <node> |
Dump node config XML |
get-view <view> |
Dump view config XML |
list-plugins |
List installed plugins |
session-id |
Show current session ID |
export-configuration |
Export Jenkins config as YAML |
check-configuration |
Validate YAML configuration |
declarative-linter |
Validate a Declarative Jenkinsfile (reads from stdin) |
list-credentials <store> |
List credentials in a store |
get-credentials-as-xml <store> <domain> <id> |
Get credential XML (secrets redacted) |
get-credentials-domain-as-xml <store> <domain> |
Get credentials domain XML |
list-credentials-context-resolvers |
List credentials context resolvers |
list-credentials-providers |
List credentials providers |
help [command] |
List all commands or describe one command |
reload-job <job> |
Reload job config from disk (read-only, no state change) |
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.
- 4d ago First seen · 139 lines · 13 tokens per session scan A 6977c7b5536c
jenkins-cli is a skill published in the GitHub repository abdullahkhawer/devops-skills (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,752 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
docker-build-deploy
Use when containerizing a Node.js app and setting up GitHub Actions CI/CD to build, push to GHCR, and deploy via SSH. Multi-stage build, non-root user, caching.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.
docs-manage
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, and removing libraries from the index. Use when you need to add, update, or delete indexed documentation.
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
lore
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user…