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 FutureJJ/claude-skills --skill devops-pipelinegit clone --depth 1 https://github.com/FutureJJ/claude-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/futurejj/claude-skills/devops-pipeline)<a href="https://agentmods.dev/skills/futurejj/claude-skills/devops-pipeline"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/devops-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/futurejj/claude-skills/devops-pipeline"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/devops-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.00040 | $0.00188 |
| Opus 5.5 | $0.00016 | $0.00075 |
| Sonnet 5.5 | $0.00008 | $0.00038 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
devops-pipeline 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 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.
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
Devops Pipeline
You are an expert in devops pipeline focused on production-grade solutions.
Core Principles
- Follow industry best practices and proven patterns
- Optimize for maintainability and reliability
- Document decisions and trade-offs
- Measure before optimizing
Anti-Patterns
- Over-engineering simple solutions
- Ignoring error handling and edge cases
- Copying patterns without understanding context
- Premature optimization without profiling
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Core patterns | references/patterns.md |
Common patterns and best practices |
| Advanced topics | references/advanced.md |
Complex scenarios and optimization |
What ships with it
2 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.
- 1mo ago First seen · 29 lines · 40 tokens per session scan A 41612322cec6
devops-pipeline is a skill published in the GitHub repository FutureJJ/claude-skills (3 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 188 once invoked, about $0.0002 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-31.
Other skills, from other repositories
github-cli
Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
codex-changelog
This skill should be used when the user asks to check for new Codex CLI (codex-cli) releases, "what changed in Codex", "any Codex updates", "check codex releases", "diff the codex version", or wants Codex CLI releases reviewed for changes relevant to THIS repo's Codex bridge. Reads a locally-stored last-checked…
gh-axi
Operate GitHub through the gh-axi CLI - issues, pull requests, stacked PRs, workflow runs, workflows, releases, repositories, labels, gists, Projects (v2), Actions secrets and variables, search, and raw API access. Use whenever a task touches GitHub: listing or filing issues, reviewing or merging PRs, managing stacked…
dependency-update
Periodic dependency update run. Reads what the package manager says is outdated, upgrades what is safe, applies the code changes the new versions need, verifies, and opens one reviewable PR. Supports a read-only dry run that reports what it would do. Use when the user says "dependency update", "/dependency-update"…
production-release-gating
Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel…