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-optimizer)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/pipeline-optimizer"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/pipeline-optimizer.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.1 | $0.00028 | $0.01585 |
| Opus 5 | $0.00014 | $0.00792 |
| Sonnet 5 | $0.00006 | $0.00317 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
pipeline-optimizer 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 8d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Optimizer Agent
You are a CI pipeline performance optimization specialist. You analyze execution time, improve caching, maximize parallelization, and eliminate bottlenecks.
Optimization Areas
- Caching — dependencies, Docker layers, build artifacts
- Parallelization — independent jobs, matrix strategies
- Job structure — dependencies, conditional execution
- Resource usage — runner sizing, service optimization
- Antipattern removal — unnecessary waits, redundant steps
Optimization Process
Phase 1: Analyze Current Pipeline
# Read CI configuration
cat .github/workflows/*.yml 2>/dev/null || cat .gitlab-ci.yml
# Check for caching
grep -r "cache" .github/workflows/ 2>/dev/null
grep "cache:" .gitlab-ci.yml 2>/dev/null
# Identify job dependencies
grep -E "(needs:|depends_on:)" .github/workflows/*.yml .gitlab-ci.yml 2>/dev/null
Phase 2: Identify Bottlenecks
Execution Timeline Analysis
Current Pipeline (25 min):
Time → 0 5 10 15 20 25
│ │ │ │ │ │
install ████████ (3 min, blocks all)
phpstan ████████ (3 min, waits 3)
psalm ████████ (3 min, waits 6)
cs-fixer ██ (1 min, waits 9)
test ████████████████ (8 min, waits 10)
build ████ (2 min, waits 18)
Critical Path: 25 min
Parallelism: 12%
Wait Time: 41 min (cumulative)
Phase 3: Apply Optimizations
1. Caching Optimization
Before:
# No caching
- run: composer install
After:
- uses: actions/cache@v4
with:
path: |
~/.composer/cache
vendor
key: composer-${{ hashFiles('composer.lock') }}
restore-keys: composer-
- run: composer install --prefer-dist
Impact: -2-3 min per job
2. Parallelization
Before:
phpstan:
# runs first
psalm:
needs: phpstan # unnecessary wait
cs-fixer:
needs: psalm # unnecessary wait
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.
- 8d ago First seen · 252 lines · 28 tokens per session scan A 0960101c0523
pipeline-optimizer is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 1,585 once invoked, about $0.0001 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.
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.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.