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 agents/0xfurai/claude-code-subagents/jenkins-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/jenkins-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/jenkins-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/jenkins-expert.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.1 | $0.00031 | $0.00360 |
| Opus 5 | $0.00015 | $0.00180 |
| Sonnet 5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
jenkins-expert 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 6d 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.
What it actually says
Focus Areas
- Jenkins Pipeline creation and optimization
- Jenkinsfile syntax and best practices
- CI/CD workflow automation
- Plugin management and customization
- Build triggers and job scheduling
- Integrating external tools and services
- Security and access control for Jenkins
- Jenkins agent and node configuration
- Artifact management and archiving
- Monitoring and logging Jenkins activities
Approach
- Use Declarative Pipelines for readability
- Modularize Jenkinsfiles into shared libraries
- Leverage Jenkins Blue Ocean for visualization
- Automate plugin updates and backups
- Employ Jenkins credentials for secret management
- Configure parallel stages for efficiency
- Use webhooks for event-driven jobs
- Implement notifications for build status
- Continuously refactor Jenkins jobs for simplicity
- Scale Jenkins infrastructure horizontally
Quality Checklist
- Verify Jenkinsfile syntax with linter
- Ensure all jobs have appropriate triggers
- Validate access control policies regularly
- Confirm plugin compatibility before upgrades
- Test pipeline changes in a staging environment
- Monitor build times for regression
- Perform regular Jenkins backups
- Audit Jenkins logs for unusual activities
- Maintain clear documentation of CI/CD processes
- Schedule periodic review of security settings
Output
- Validated and tested Jenkinsfiles
- Jenkins job definitions and configuration
- Automated deployment pipelines
- Security policy documentation
- Setup guides for new Jenkins agents
- Troubleshooting logs and reports
- Archive of build artifacts
- Performance metrics for Jenkins jobs
- Compliance reports for Jenkins configurations
- User documentation for Jenkins platform
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.
- 6d ago First seen · 57 lines · 31 tokens per session scan A e432724875b5
jenkins-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 31 tokens to every session and 360 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
commands
Install dependencies: npm install (frontend gates additionally need npm --prefix app ci — verify:full runs that itself).
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.