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/skills-marketplace --skill jkgit clone --depth 1 https://github.com/avivsinai/skills-marketplaceWrote 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/skills-marketplace/jk)<a href="https://agentmods.dev/skills/avivsinai/skills-marketplace/jk"><img src="https://agentmods.dev/badge/skills/avivsinai/skills-marketplace/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/skills-marketplace/jk"><img src="https://agentmods.dev/badge/skills/avivsinai/skills-marketplace/jk.svg" alt="Reviewed on agentmods" width="80" 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.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 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.
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.
This is a copy
100% identical to jk — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 4d ago Changed 7a5f592dfe96
- 13d ago Changed c55e341a0c68
- 18d ago Changed 0964fcc479c3
- 22d ago Changed c57d39a1c2d3
- 1mo ago Changed 906a05c3d3bd
- 1mo ago Changed · -369 lines · -52 tokens per session ad5eb8e3d212
- 2mo ago First seen · 451 lines · 78 tokens per session scan A 9a44dfe2c00d
jk is a skill published in the GitHub repository avivsinai/skills-marketplace (2 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. It is 100% identical to jk, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github-actions-cicd
Design, review, or debug GitHub Actions workflows — CI jobs (type-check, lint, test, build, security, summary), AWS ECR/ECS deploys, and a standardized per-repo workflow set. NOT for cloud-auth role/OIDC trust details (use aws-cicd-auth) or Dockerfile/image-build mechanics (use docker-build).
aws-cicd-auth
Configure and review AWS auth for GitHub Actions CI/CD — OIDC role assumption, ECR push perms, ECS deploy perms, least-privilege IAM. Not for application IAM/Cognito, not for GCP.
gcp-cicd-auth
Configure and review GCP authentication for GitLab CI/CD pipelines: Workload Identity Federation, Artifact Registry push, Secret Manager access, and least-privilege service accounts. Not for Keycloak IAM, AWS/Azure auth, or runtime pod identity.
gitlab-ci-cd
Design, review, or debug .gitlab-ci.yml pipelines for the project's repos. Covers stage ordering, job configuration, artifact flow, deploy safety flags, and the 8-stage model. Not for GitHub Actions, Jenkins, GitOps controllers, or GCP auth stanzas.
troubleshooting
Debug a specific failure, investigate an incident, analyze error logs, or diagnose connectivity on the project's platform. NOT for proactive instrumentation (use monitoring/observability) or writing tests (use testing).
supply-chain-security
Audit and harden container supply-chain controls: image scanning, SBOM generation, immutable digest promotion, rollback retention, and image signing readiness. Not for application code vulnerabilities (use security-audit) or pipeline YAML structure (use deployment).