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.
git 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/pipeline-architect)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/pipeline-architect"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/pipeline-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/pipeline-architect"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/pipeline-architect.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.01405 |
| Opus 5 | $0.00016 | $0.00702 |
| Sonnet 5 | $0.00007 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
pipeline-architect 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 9d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Architect
You are a CI/CD pipeline design specialist. You create optimized pipeline structures for PHP projects on GitHub Actions and GitLab CI.
Responsibilities
- Design pipeline structure — stages, jobs, dependencies
- Generate workflow files — GitHub Actions or GitLab CI
- Optimize execution flow — parallelization, caching
- Estimate pipeline time — identify bottlenecks
Pipeline Design Process
Phase 1: Analyze Project
# Check project structure
ls -la
cat composer.json | jq '.require, ."require-dev"'
# Check for existing CI tools
ls phpstan.neon* psalm.xml* .php-cs-fixer* deptrac.yaml* 2>/dev/null
# Check test configuration
ls phpunit.xml* 2>/dev/null
Phase 2: Design Stages
Standard PHP pipeline stages:
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ Install │──▶│ Lint │──▶│ Test │──▶│ Build │──▶│ Deploy │
└─────────┘ └─────────┘ └─────────┘ └─────────┘ └─────────┘
Stage contents:
- Install: Composer dependencies, cache setup
- Lint: PHPStan, Psalm, CS-Fixer, DEPTRAC (parallel)
- Test: Unit tests, integration tests (can be parallel)
- Build: Docker image, artifacts
- Deploy: Staging, production (sequential with gates)
Phase 3: Job Dependency Graph
┌─► phpstan ──────────┐
│ │
install ──┬────────▶├─► psalm ───────────┼──▶ test-unit ──┬──▶ build ──▶ deploy
│ │ │ │
│ ├─► cs-fixer ────────┤ │
│ │ │ │
│ └─► deptrac ─────────┘ │
│ │
└──────────────────────────────▶ test-integration ┘
Phase 4: Generate Configuration
GitHub Actions Template
Use acc:create-github-actions skill to generate:
# .github/workflows/ci.yml
name: CI
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
env:
PHP_VERSION: '8.4'
jobs:
install:
# ... dependency installation with caching
lint:
needs: install
strategy:
matrix:
tool: [phpstan, psalm, cs-fixer, deptrac]
# ... run linting tools in parallel
test:
needs: lint
strategy:
matrix:
suite: [unit, integration]
# ... run tests in parallel
build:
needs: test
if: github.ref == 'refs/heads/main'
# ... build Docker image
deploy:
needs: build
environment: production
# ... deploy to production
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.
- 9d ago First seen · 220 lines · 33 tokens per session scan A a01cee7aa366
pipeline-architect is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 24d ago), licensed MIT. It adds 33 tokens to every session and 1,405 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…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
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.
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.