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 avivsinai/jenkins-cli --skill jkgit clone --depth 1 https://github.com/avivsinai/jenkins-cliWrote 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/avivsinai/jenkins-cli/jk)<a href="https://agentmods.dev/skills/avivsinai/jenkins-cli/jk"><img src="https://agentmods.dev/badge/skills/avivsinai/jenkins-cli/jk/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/avivsinai/jenkins-cli/jk"><img src="https://agentmods.dev/badge/skills/avivsinai/jenkins-cli/jk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 70 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 357 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00026 | $0.00750 |
| Opus 5.5 | $0.00010 | $0.00300 |
| Sonnet 5.5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
jk 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- jk — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jenkins CLI
Use jk for Jenkins reads and changes. Inspect jk --help or a subcommand's
help when syntax is uncertain. Check installation or version only when the
command is unavailable or a requested feature has a known minimum version.
Route the task
Read only the rule that matches the request:
- Authentication and SSO: rules/auth.md
- Saved controllers and context selection: rules/context.md
- Jobs, folders, configuration, and scans: rules/job.md
- Runs, parameters, reruns, and logs: rules/run.md
- Artifacts: rules/artifact.md
- Test reports: rules/test.md
- Credentials: rules/cred.md
- Nodes: rules/node.md
- Queue: rules/queue.md
- Plugins: rules/plugin.md
- Other administrative commands: rules/other.md
For exact flags and output modes, search references/commands.md for the subcommand.
Shared operating rules
- Use the active context unless the user names another controller. Verify the target context before a state-changing or security-sensitive operation.
- Prefer structured output (
--jsonor--yaml) when another tool or script will consume the result. - Inspect a job's declared parameters before starting a parameterized run; do not guess names or values.
- Treat job configuration, credentials, nodes, plugins, queue cancellation, and run deletion as state-changing operations. Show the resolved target and follow the user's authorization.
- Never print, store, or echo Jenkins tokens or credential secrets. Browser SSO access tokens are not Jenkins API tokens; follow rules/auth.md.
- Do not weaken TLS verification unless the user explicitly chooses that risk.
Common reads
jk job ls
jk job view team/app
jk run ls team/app
jk run view team/app 128
jk log team/app 128 --follow
jk artifact ls team/app 128
jk test report team/app 128
jk queue ls
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed c55e341a0c68
- 8d ago Changed 0964fcc479c3
- 12d ago Changed c57d39a1c2d3
- 1mo ago Changed 906a05c3d3bd
- 1mo ago Changed · -369 lines · -52 tokens per session ad5eb8e3d212
- 1mo ago First seen · 451 lines · 78 tokens per session scan A 9a44dfe2c00d
jk is a skill published in the GitHub repository avivsinai/jenkins-cli (95 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 750 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-30.
Other skills, from other repositories
golang-continuous-integration
CI/CD pipeline configuration using GitHub Actions for Golang projects — testing, linting, SAST, security scanning, code coverage, Dependabot, Renovate, GoReleaser, code review automation, and release pipelines. Use when setting up or improving Go project CI, configuring GitHub Actions workflows, adding linters or…
amq-cli
Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.
amq-spec
Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.
ci-failures
Summarizes failing CI jobs for a pull request. Use when asked why a PR build is red.
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
go-ci-workflow
Use when creating or refactoring GitHub Actions CI workflows for Go repositories. Covers repository-shape detection, Make-driven delegation with formal fallbacks, Go setup, caching, tool pinning, permissions, reusable workflows, and quality gate design.