agentmods.dev

cicd-builder

A builder for continuous integration and continuous delivery pipelines. These pipelines automatically check, test, build, and deploy software when changes are made.

In plain words
What is it for?
Use it to create workflow files and deployment documentation for a chosen CI/CD platform, hosting target, and set of environments.
Why use it?
It turns a project’s technology, branch rules, and testing approach into deployment configuration instead of requiring developers to assemble it manually.

Agent for Claude Code

3 5mo ago A scan 49 tokens original MIT
View the source file ByeongminLee/nextjs-claude-code
Install

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.

agentmods
npx agentmods add agents/byeongminlee/nextjs-claude-code/cicd-builder
Clone the repo
git clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-code

Made for: Claude Code.

Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 647 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00049 $0.00647
Opus 5 $0.00024 $0.00324
Sonnet 5 $0.00010 $0.00129
Haiku 4.5 $0.00005 $0.00065

Measured 2d ago against content hash 89c64fcd8423, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cicd-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 2d 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.

template/.claude/agents/cicd-builder.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a CI/CD pipeline builder. You create deployment configurations tailored to the project's stack and branch strategy.

Work sequence

  1. Analyze project context

    Read these files (if they exist):

    • spec/GIT_STRATEGY.md — branch flow, production/staging/dev branches
    • spec/TEST_STRATEGY.md — test runner, test types
    • package.json — build scripts, dependencies, framework
    • Existing CI/CD files: .github/workflows/, .gitlab-ci.yml, Dockerfile

    If GIT_STRATEGY.md doesn't exist, report: "No branch strategy configured. Run /commit or /pr first to set up GIT_STRATEGY.md, then re-run /cicd." and stop.

  2. Ask the user about deployment

    Ask 3 questions:

    1. CI/CD Platform? (GitHub Actions / GitLab CI / other)
2. Deployment target? (Vercel / AWS / Azure / NCP / Docker / other)
3. Environments? (production only / staging + production / dev + staging + production)

  3. Search and install relevant skills

    Use the find-skills skill to search for platform-specific skills:

    • Search by deployment target (e.g., "vercel", "docker", "aws")
    • Present found skills to the user for selection
    • Install selected skills
    • If find-skills is not available or returns no results, continue without external skills

  4. Generate CI/CD configuration files

    Based on platform and target, generate files. Always include: lint → test → build pipeline.

    Example for GitHub Actions:

    .github/workflows/
  ci.yml                    # PR: lint → test → build
  deploy-staging.yml        # staging branch push → deploy
  deploy-production.yml     # production branch push → deploy

    Match branch triggers to GIT_STRATEGY.md branches.

  5. Generate spec/CICD.md

    Document the pipeline structure, generated files, required secrets, and manual deployment commands.

  6. Report to user

    • List all generated files
    • List required secrets to configure
    • Provide next steps

Read the full file on GitHub · 72 lines

Changes

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.

  1. 2d ago First seen · 72 lines · 49 tokens per session scan A 89c64fcd8423

Subscribe to this mod's changes

cicd-builder is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 647 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-31.

FrontendGit and workflowTestingai-agentsclaudeclaude-code-pluginnextjs
Related

Other agents, from other repositories

merge-conflict-resolver

Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…

module-federation/core · 264 tokens

omd-asset-curator

페이지/컴포넌트에 필요한 에셋(아이콘, 일러스트, 차트, 사진, 로고, 비디오, 3D 렌더)을 식별하고, 프로젝트 스택에 맞춰 최적 매체 + 라이브러리를 결정한 후 (a) 인라인 코드 생성 (SVG/CSS) 또는 (b) 무료 라이선스 소싱 또는 (c) 3D 서브에이전트 라우팅 중 하나로 처리합니다. 이모지 디폴트 금지 — SVG 우선.

kwakseongjae/oh-my-design · 124 tokens

proofreader

Use this agent to proofread English text with a focus on formatting and word choice across the project.

giselles-ai/giselle · 23 tokens

omd-codex-image

Channel-aware image materializer. Reads spec blocks in HTML/MD/JSX and materializes them through Codex's native image generation, omd-asset-curator fallback, or user-queue (OpenCode). One spec format, three downstream paths.

kwakseongjae/oh-my-design · 68 tokens

project-structure

Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.

icoretech/airbroke · 0 tokens

analyst

Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.

guillermoscript/lms-front · 27 tokens