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 eea/eea.agent.skills --skill jenkins-pipelinegit clone --depth 1 https://github.com/eea/eea.agent.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/eea/eea.agent.skills/jenkins-pipeline)<a href="https://agentmods.dev/skills/eea/eea.agent.skills/jenkins-pipeline"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/jenkins-pipeline/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/eea/eea.agent.skills/jenkins-pipeline"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/jenkins-pipeline.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.00049 | $0.16840 |
| Opus 5 | $0.00024 | $0.08420 |
| Sonnet 5 | $0.00010 | $0.03368 |
| Haiku 4.5 | $0.00005 | $0.01684 |
Grade A, and why
jenkins-pipeline 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 10d 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.
response=$(curl -s -w "\\n%{http_code}" -XPOST -u "${SONAR_AUTH_TOKEN}:" "${SONAR_HOST_URL}api/alm_settings/set_github_binding" \ How it starts
The opening of the file, as written. The whole thing — 1,336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jenkins Pipeline
Create Jenkins declarative pipelines that match EEA's Jenkinsfile structure and operational constraints.
When to use
Use this skill when you need to create or update:
Jenkinsfile- Docker-based CI test pipelines
- SonarQube and Trivy quality gates
- Docker Hub release automation
- reusable CI layouts for JavaScript, Python, or mixed application repositories
- developer-reproducible Docker test flows that match Jenkins exactly
- README CI/quality badges (Jenkins pipeline, SonarQube) — raised proactively once the Jenkinsfile is finalized (see the EEA-specific override for when and why), as a conversation about which badges and branch rather than a template to apply blindly
- diagnosing and fixing a failed Jenkins build — see
references/diagnosing-failed-builds.md
Required workflow
This is a strict order, not a menu — do not generate the Jenkinsfile before completing every earlier phase, and do not skip the preflight because the repository "looks fine." The whole point of the preflight is that a Jenkinsfile written before it is a guess about what will pass in CI; a Jenkinsfile written after it is a fact.
Phase 1 — Discover
- Inspect the repository and identify:
- package manager / build tool
- lint / type-check commands
- unit test commands
- integration / e2e test commands
- coverage output capabilities
- Docker build context and release image details
- the repository's actual default branch (
git remote show origin | grep 'HEAD branch', orgh repo view --json defaultBranchRef) — don't assumemain; plenty of EEA repos still default tomaster, and getting this wrong means every "default branch" check in the generated Jenkinsfile (the Docker Hub release gate, the:latesttag, the untagged-IMAGE_TAGfallback) silently never fires - whether this repo fits the Docker-based JS/Python default at all, or
matches one of the alternate real shapes in
references/examples/instead (Java/Maven via Jenkins tool installations, a Python egg/Plone add-on, a Dockerfile-only release repo). Decide this now — it changes what Phase 2 means, not just what Phase 4 generates.
What ships with it
8 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.
- references/diagnosing-failed-builds.md 8.4 KB
- references/dockerfile-test-template.md 996 B
- references/eea-available-plugins.md 3.5 KB
- references/eea-jenkinsfile-template.md 9.6 KB
- references/examples/docker-helm-release-jenkinsfile.md 3.5 KB
- references/examples/java-maven-jenkinsfile.md 9.9 KB
- references/examples/nodejs-volto-jenkinsfile.md 23 KB
- references/examples/python-egg-plone-jenkinsfile.md 13 KB
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.
- 10d ago First seen · 1,336 lines · 49 tokens per session scan A e19b1719b048
jenkins-pipeline is a skill published in the GitHub repository eea/eea.agent.skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 16,840 once invoked, about $0.0002 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
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
devops-automator
Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use…
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
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.