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 selvarajmurugesan90/ops-engineering-skills --skill jenkins-declarative-pipeline-per-repogit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-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/selvarajmurugesan90/ops-engineering-skills/jenkins-declarative-pipeline-per-repo)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/jenkins-declarative-pipeline-per-repo"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/jenkins-declarative-pipeline-per-repo/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/selvarajmurugesan90/ops-engineering-skills/jenkins-declarative-pipeline-per-repo"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/jenkins-declarative-pipeline-per-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
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 →
- medium Agent Snooping · line 29 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 225 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 341 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 342 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00111 | $0.03348 |
| Opus 5.5 | $0.00044 | $0.01339 |
| Sonnet 5.5 | $0.00022 | $0.00670 |
| Haiku 4.5 | $0.00011 | $0.00335 |
Grade A, and why
jenkins-declarative-pipeline-per-repo 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 1mo 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.
curl -s -X POST -u ${JENKINS_USER}:${JENKINS_API_TOKEN} \ How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jenkins Declarative Pipeline Per Repo
Purpose
A per-repo Jenkinsfile puts pipeline-as-code directly in the repository it
builds: it's reviewed in the same pull request as the code change, versioned
alongside it, and doesn't require a Jenkins administrator to touch a
separate job configuration. This skill covers Jenkins Declarative
Pipeline syntax specifically — the agent/stages/steps/post block
structure, environment and when conditionals, and the concrete
constructs (not generic CI concepts, which are covered in
ci-cd-pipeline-design)
needed to write a correct, maintainable Jenkinsfile that lives in a single
repo. It also covers the specific trade-off of the per-repo model versus
centralizing logic in a shared library, so a team can make an informed
choice rather than defaulting to copy-paste.
When to use
- A repository has no Jenkinsfile yet and needs one for build/test/package.
- An existing per-repo Jenkinsfile is failing at a specific stage and needs
debugging (syntax error, wrong
agentlabel, awhencondition that never matches). - Adding a
postblock for Slack/email notification on failure, or aalwayscleanup step (e.g.deleteDir()), to an existing pipeline. - Deciding whether pipeline logic that's growing complex in one Jenkinsfile should stay per-repo or be extracted into a shared library — see jenkins-centralized-shared-library for that migration.
- Reviewing a Jenkinsfile PR and needing to know whether
sh,script, or a plugin step is idiomatic for a given task.
Prerequisites & environment
- A Jenkins controller (2.401+ LTS recommended for current Declarative
Pipeline features) with the Pipeline plugin suite installed
(
workflow-aggregator), which ships Declarative Pipeline support. - The repo is registered as a Multibranch Pipeline or Pipeline job
with "Pipeline script from SCM" pointing at
Jenkinsfilein the repo root (or a path configured in the job) — the Jenkinsfile is not useful without a job/multibranch config that reads it from SCM. - Build agents (nodes) with the required labels available — e.g. a
dockerorlinux-x64label matching what the Jenkinsfile'sagentblock requests. Confirm labels via Manage Jenkins → Nodes. - Credentials (SSH keys, registry tokens, cloud creds) already created in
Manage Jenkins → Credentials with known IDs — a Jenkinsfile only
references a credential ID (
${JENKINS_CRED_ID}), it never stores the secret value itself. - For Docker-based agents: the controller/agent has Docker available and
the
Docker Pipelineplugin installed if usingagent { docker { ... } }.
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.
- 1mo ago First seen · 343 lines · 111 tokens per session scan A 3fc147ca6256
jenkins-declarative-pipeline-per-repo is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (43 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 3,348 once invoked, about $0.0004 per session on Opus 5.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-30.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
ci-fixer
CI failures - read error, minimal fix, verify.