ci-setup

ci-setup is a command for coding agents from davepoon/buildwithclaude. It costs 4 tokens per session (1,993 once invoked), scanned A, original, MIT.

A command for setting up continuous integration and delivery (CI/CD), the automated process that checks code and can prepare it for release. It covers repository settings, build pipelines, tests, and deployment environments.

In plain words
What is it for?
Use it to analyse a project's technology and deployment needs, choose a CI/CD platform, configure repository rules, and create a build pipeline.
Why use it?
It gives a structured way to connect code changes with automated checks and delivery instead of configuring each part ad hoc.

Command

About the project

davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.

davepoon/buildwithclaude · 3,415 stars · on GitHub

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 commands/davepoon/buildwithclaude/ci-setup
Clone the repo
git clone --depth 1 https://github.com/davepoon/buildwithclaude

Wrote 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.

agentmods badge for ci-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/davepoon/buildwithclaude/ci-setup.svg)](https://agentmods.dev/commands/davepoon/buildwithclaude/ci-setup)
Your own site
<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/ci-setup"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/ci-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,993 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.00004 $0.01993
Opus 5 $0.00002 $0.00996
Sonnet 5 $0.00001 $0.00399
Haiku 4.5 $0.00000 $0.00199

Measured today against content hash 5a19ce695f62, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ci-setup 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 today.

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.

plugins/all-commands/commands/ci-setup.md · 315 lines

How it starts

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

CI/CD Setup Command

Setup continuous integration pipeline

Instructions

Follow this systematic approach to implement CI/CD: $ARGUMENTS

  1. Project Analysis

    • Identify the technology stack and deployment requirements
    • Review existing build and test processes
    • Understand deployment environments (dev, staging, prod)
    • Assess current version control and branching strategy
  2. CI/CD Platform Selection

    • Choose appropriate CI/CD platform based on requirements:
      • GitHub Actions: Native GitHub integration, extensive marketplace
      • GitLab CI: Built-in GitLab, comprehensive DevOps platform
      • Jenkins: Self-hosted, highly customizable, extensive plugins
      • CircleCI: Cloud-based, optimized for speed
      • Azure DevOps: Microsoft ecosystem integration
      • AWS CodePipeline: AWS-native solution
  3. Repository Setup

    • Ensure proper .gitignore configuration
    • Set up branch protection rules
    • Configure merge requirements and reviews
    • Establish semantic versioning strategy
  4. Build Pipeline Configuration

    GitHub Actions Example:

    name: CI/CD Pipeline
    
    on:
      push:
        branches: [ main, develop ]
      pull_request:
        branches: [ main ]
    
    jobs:
      test:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v3
          - name: Setup Node.js
            uses: actions/setup-node@v3
            with:
              node-version: '18'
              cache: 'npm'
          - run: npm ci
          - run: npm run test
          - run: npm run build
    

    GitLab CI Example:

    stages:
      - test
      - build
      - deploy
    
    test:
      stage: test
      script:
        - npm ci
        - npm run test
      cache:
        paths:
          - node_modules/
    
  5. Environment Configuration

    • Set up environment variables and secrets
    • Configure different environments (dev, staging, prod)
    • Implement environment-specific configurations
    • Set up secure secret management

Read the full file on GitHub · 315 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. today First seen · 315 lines · 4 tokens per session scan A 5a19ce695f62

Subscribe to this mod's changes

ci-setup is a command published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 1,993 once invoked, about $0.0000 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-09-05.