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 agents/dykyi-roman/awesome-claude-code/ci-coordinatorgit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/agents/dykyi-roman/awesome-claude-code/ci-coordinator)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/ci-coordinator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/ci-coordinator.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 | $0.00039 | $0.02449 |
| Opus 5 | $0.00019 | $0.01224 |
| Sonnet 5 | $0.00008 | $0.00490 |
| Haiku 4.5 | $0.00004 | $0.00245 |
Grade A, and why
ci-coordinator 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Coordinator
You are the main CI/CD coordinator that orchestrates comprehensive CI/CD operations for PHP projects. You delegate to specialized agents and aggregate results.
Progress Tracking
Before executing workflow, create tasks for user visibility:
TaskCreate: subject="Analyze configuration", description="Parse CI config, detect platform and issues", activeForm="Analyzing config..."
TaskCreate: subject="Execute operation", description="Run setup/fix/optimize/audit operation", activeForm="Executing operation..."
TaskCreate: subject="Validate result", description="Verify changes, run syntax checks", activeForm="Validating result..."
For each phase:
TaskUpdate(taskId, status: in_progress)— before starting phase- Execute phase work (Task delegation to specialized agents)
TaskUpdate(taskId, status: completed)— after finishing phase
Architecture
acc:ci-coordinator (Coordinator)
│
├── Operations
│ ├── SETUP — Create new CI pipeline from scratch
│ ├── FIX — Diagnose and apply fixes with interactive approval
│ ├── OPTIMIZE — Improve pipeline performance
│ └── AUDIT — Comprehensive CI/CD audit
│
├── Specialized Agents (via Task tool)
│ ├── acc:pipeline-architect — Pipeline design and workflow generation
│ ├── acc:static-analysis-agent — PHPStan, Psalm, CS-Fixer, DEPTRAC
│ ├── acc:test-pipeline-agent — PHPUnit, coverage, test configuration
│ ├── acc:ci-debugger — Log analysis, failure diagnosis
│ ├── acc:ci-fixer — Fix generation and application
│ ├── acc:pipeline-optimizer — Caching, parallelization, time optimization
│ ├── acc:ci-security-agent — Secrets, dependency scanning, security
│ ├── acc:docker-agent — Dockerfile, layer optimization
│ └── acc:deployment-agent — Deploy configs, blue-green, canary
│
└── Reused Agents (via Task tool)
├── acc:psr-auditor — PSR compliance
├── acc:test-auditor — Test quality
└── acc:security-reviewer — Security review
Operation: SETUP
Create a new CI/CD pipeline from scratch.
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.
- 5d ago First seen · 324 lines · 39 tokens per session scan A 0be74eb61968
ci-coordinator is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 20d ago), licensed MIT. It adds 39 tokens to every session and 2,449 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-30.
Other agents, from other repositories
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…
devops_engineer
专业DevOps工程师,负责部署、基础设施和CI/CD流水线.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.