Borrowing it
Nothing to install: this file belongs to afaizalam2003/Master-claude-skill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/afaizalam2003/Master-claude-skill/main/.gemini/skills/ci-cd-pipeline-builder/SKILL.mdgit clone --depth 1 https://github.com/afaizalam2003/Master-claude-skillWrote 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/afaizalam2003/master-claude-skill/ci-cd-pipeline-builder)<a href="https://agentmods.dev/skills/afaizalam2003/master-claude-skill/ci-cd-pipeline-builder"><img src="https://agentmods.dev/badge/skills/afaizalam2003/master-claude-skill/ci-cd-pipeline-builder/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/afaizalam2003/master-claude-skill/ci-cd-pipeline-builder"><img src="https://agentmods.dev/badge/skills/afaizalam2003/master-claude-skill/ci-cd-pipeline-builder.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.00000 | $0.00013 |
| Opus 5 | $0.00000 | $0.00006 |
| Sonnet 5 | $0.00000 | $0.00003 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
ci-cd-pipeline-builder 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 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.
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 ci-cd-pipeline-builder — 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.
What it actually says
../../../engineering/ci-cd-pipeline-builder/SKILL.md
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 lines · 0 tokens per session scan A fecef9fd08cd
ci-cd-pipeline-builder is a skill published in the GitHub repository afaizalam2003/Master-claude-skill (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 13 tokens. A static security scan graded it A with 0 findings. It is 100% identical to ci-cd-pipeline-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
repo-scaffold
Scaffold or standardize a production-ready repository structure with specs, source layout, tests, CI, agent context, config examples, release notes, and operational docs. Use when starting a new repo, turning a prototype into a maintainable project, adding missing repository foundations, or creating a repo skeleton…
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
lov-npm-publisher
An npm package publishing workflow that sets up releases through GitHub Actions using OIDC, a login-free trust method, or a local granular NPM token. It covers initial setup, publishing, audit checks, and verifying the package on the npm registry.
gh-ci-analyzer
A guide for using GitHub’s command-line tool to investigate failed GitHub Actions runs. GitHub Actions is GitHub’s system for automatically building, testing, and deploying code.
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
ci
This skill should be used when the user asks about "CI pipeline", "continuous integration", "GitHub Actions", "CI configuration", "CI jobs", "workflow", "CI caching", "CI environment", "pipeline structure", or needs guidance on setting up or configuring CI/CD pipelines.