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 skills/new1direction/korgex/ci-cd-pipelinesnpx skills add New1Direction/korgex --skill ci-cd-pipelinesgit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/ci-cd-pipelines)<a href="https://agentmods.dev/skills/new1direction/korgex/ci-cd-pipelines"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/ci-cd-pipelines.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.00015 | $0.00327 |
| Opus 5 | $0.00008 | $0.00163 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
ci-cd-pipelines 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
CI/CD makes quality automatic: every change is built, tested, and (when trusted) shipped the same way, every time.
- CI gates merges. On every push/PR, run: install → lint → build → test. The pipeline is the source of truth for "is this mergeable" — keep it green and treat a red build as stop-the-line.
- Make it fast and deterministic. Cache dependencies; parallelize independent jobs; pin tool versions so runs are reproducible. A slow or flaky pipeline gets ignored.
- No flaky gates. A test that fails intermittently erodes trust in the whole pipeline — fix or quarantine it (see condition-based-waiting for the usual cause).
- CD ships the artifact CI built — don't rebuild for deploy. Promote the exact tested artifact through environments (e.g. staging → prod).
- Secrets via the CI secret store, never in the config or logs. Scope them to the jobs that need them.
- Match the project. Use its existing CI system and config conventions; add a job, don't introduce a second CI tool.
- Surface results where people see them (status checks, required checks on the default branch) so the gate actually gates.
Pair with deploying-safely for what happens after the pipeline goes green.
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 · 28 lines · 15 tokens per session scan A 9ebab3358ef5
ci-cd-pipelines is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 327 once invoked, about $0.0001 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-31.
Other skills, from other repositories
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Use the GitHub app from this plugin for PR metadata and patch context, and use gh for Actions check and log inspection before implementing any approved fix.
ci-self-heal
针对 CI 失败日志输出结构化诊断与修复建议. 识别失败分类(test/lint/build/type/dependency/config/flaky/timeout) / 根因假设 / 可执行 fix, 引用具体 file:line. 专为 PR-to-Prod 流程的 CI 卡点兜底设计.
ci-debugger
Use when the user asks to diagnose or fix a CI, build, test, packaging, or deployment pipeline failure. 用户提到排查 CI、构建失败、测试失败、打包失败或部署流水线时使用。 Inspect the actual failed job, logs, configuration, inputs, cache, and local reproduction path before changing code or retrying jobs; distinguish infrastructure failures from…
ci-cd-and-automation
Design CI/CD pipelines with fast feedback, quality gates, and reliable deployments.
dsh-ci-test-reliability
Design, review, and diagnose DeepSeek Harness tests and fixtures that can fail nondeterministically under CI concurrency, shared host resources, clocks, process-global state, subprocesses, network listeners, or asynchronous teardown. Use when adding or changing tests with those risks, investigating flaky CI, or…
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.