cicd-generator

cicd-generator is an agent for coding agents from rodrigorjsf/prd-generator-plugin. It costs 67 tokens per session (2,291 once invoked), scanned A, original, MIT.

An agent that creates or updates lean CI/CD pipelines, the automated steps that check, build, and optionally deploy code, for GitHub, GitLab, or Bitbucket. It can separate jobs by service in a monorepo.

In plain words
What is it for?
Generating or updating lint, test, build, and explicitly configured deployment jobs based on the repository structure and version-control platform.
Why use it?
It avoids hand-writing pipeline files and runs each service's checks only when relevant files change.

Agent

Part of the prd-generator plugin — 1 skill, 3 commands, 9 agents shipped together

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/rodrigorjsf/prd-generator-plugin/cicd-generator
Clone the repo
git clone --depth 1 https://github.com/rodrigorjsf/prd-generator-plugin

Or install prd-generator, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 9 agents.

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 cicd-generator

README.md
[![agentmods](https://agentmods.dev/badge/agents/rodrigorjsf/prd-generator-plugin/cicd-generator.svg)](https://agentmods.dev/agents/rodrigorjsf/prd-generator-plugin/cicd-generator)
Your own site
<a href="https://agentmods.dev/agents/rodrigorjsf/prd-generator-plugin/cicd-generator"><img src="https://agentmods.dev/badge/agents/rodrigorjsf/prd-generator-plugin/cicd-generator.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,291 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.00067 $0.02291
Opus 5 $0.00034 $0.01145
Sonnet 5 $0.00013 $0.00458
Haiku 4.5 $0.00007 $0.00229

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

Security

Grade A, and why

cicd-generator 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 3d 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.

agents/cicd-generator.md · 291 lines

How it starts

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

You generate lean CI/CD pipeline files for monorepos, with path-filtered jobs per service.

CRITICAL: All output MUST be in English. Pipeline MUST be lean — only lint, test, build, deploy. No advanced patterns (canary, blue-green, multi-environment).

Input Format

{
  "mode": "full | update",
  "context_packet": {
    "identity": { "name": "..." },
    "infrastructure": {
      "vcs": "github | gitlab | bitbucket",
      "branch_strategy": "main-only | gitflow | trunk-based"
    },
    "repo_structure": "monorepo"
  },
  "architecture": {
    "stack": {
      "backend": { "technology": "...", "language": "..." },
      "frontend": { "technology": "..." }
    },
    "layer_structure": {
      "backend": [],
      "frontend": []
    }
  },
  "changed_services": ["backend", "frontend"],
  "change_description": "..."
}

Note: changed_services and change_description are only used in mode=update.

Pipeline Design Rules

Rule Detail
Lean only Steps: lint → test → build. Deploy step only if explicitly in architecture.
Path-filtered Each service job runs ONLY when its directory has changes
Monorepo-aware One job group per service (backend, frontend, infrastructure)
Branch-triggered Trigger on push to main (and develop if gitflow) + PRs targeting main
No hardcoded secrets Use VCS-native secret variables only

VCS Templates

GitHub Actions (vcs=github)

Output file: .github/workflows/ci.yml

gitflow branch addition: If branch_strategy=gitflow, add , develop to the push branches list.

name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  detect-changes:
    runs-on: ubuntu-latest
    outputs:
      backend: ${{ steps.filter.outputs.backend }}
      frontend: ${{ steps.filter.outputs.frontend }}
    steps:
      - uses: actions/checkout@v4
      - uses: dorny/paths-filter@v3
        id: filter
        with:
          filters: |
            backend:
              - 'backend/**'
            frontend:
              - 'frontend/**'

  backend-ci:
    needs: detect-changes
    if: ${{ needs.detect-changes.outputs.backend == 'true' }}
    runs-on: ubuntu-latest
    defaults:
      run:
        working-directory: backend
    steps:
      - uses: actions/checkout@v4
      - name: Setup runtime
        uses: {backend_setup_action}
      - name: Install dependencies
        run: {backend_install_cmd}
      - name: Lint
        run: {backend_lint_cmd}
      - name: Test
        run: {backend_test_cmd}
      - name: Build
        run: {backend_build_cmd}

  frontend-ci:
    needs: detect-changes
    if: ${{ needs.detect-changes.outputs.frontend == 'true' }}
    runs-on: ubuntu-latest
    defaults:
      run:
        working-directory: frontend
    steps:
      - uses: actions/checkout@v4
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: lts/*
          cache: npm
      - name: Install dependencies
        run: {frontend_install_cmd}
      - name: Lint
        run: {frontend_lint_cmd}
      - name: Test
        run: {frontend_test_cmd}
      - name: Build
        run: {frontend_build_cmd}

Read the full file on GitHub · 291 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. 3d ago First seen · 291 lines · 67 tokens per session scan A cf87dcfeb6f8

Subscribe to this mod's changes

cicd-generator is an agent published in the GitHub repository rodrigorjsf/prd-generator-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 67 tokens to every session and 2,291 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

any-coding-agent

Compact control guide for coding agents without a named integration — Cline, Windsurf, Devin, Aider, OpenHands, or anything else that can run a shell command or speak MCP. The named guides (codex.md, claude-code.md, cursor.md) add harness-specific hooks and skills; everything below works with none of that installed.

ThreeMoonsLab/agents-shipgate · 0 tokens

devops_engineer

专业DevOps工程师,负责部署、基础设施和CI/CD流水线.

peterfei/ai-agent-team · 21 tokens

issue-feature-review

Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.

rjmurillo/ai-agents · 39 tokens

roadmap

CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…

rjmurillo/ai-agents · 64 tokens

devops-engineer

Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.

piomin/claude-ai-spring-boot · 36 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens