everything-react-native-expo: Agent for Claude Code

.claude/agents/pipeline-orchestrator.md

pipeline-orchestrator is an agent for Claude Code from JubaKitiashvili/everything-react-native-expo. It costs 33 tokens per session (1,695 once invoked), scanned A, original, MIT.

A coordination agent for multi-agent coding workflows. It sequences tasks, sends work to the appropriate agents, manages handoffs, retries failed work, and escalates blockers.

In plain words
What is it for?
Use it to coordinate a pipeline from planning through implementation and delivery, including parallel work, handoffs, retries, and status tracking.
Why use it?
It prevents agents from working in the wrong order or losing important information between stages.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is JubaKitiashvili/everything-react-native-expo's own configuration. It tells Claude Code how to work on everything-react-native-expo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything everything-react-native-expo configures →

Part of the erne-universal plugin — 45 skills, 12 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to JubaKitiashvili/everything-react-native-expo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JubaKitiashvili/everything-react-native-expo/main/.claude/agents/pipeline-orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/JubaKitiashvili/everything-react-native-expo

Made for: Claude Code.

Or install erne-universal, the plugin that ships this one along with the rest of its 45 skills, 12 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 pipeline-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/jubakitiashvili/everything-react-native-expo/pipeline-orchestrator/github.svg)](https://agentmods.dev/agents/jubakitiashvili/everything-react-native-expo/pipeline-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/jubakitiashvili/everything-react-native-expo/pipeline-orchestrator"><img src="https://agentmods.dev/badge/agents/jubakitiashvili/everything-react-native-expo/pipeline-orchestrator/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.

agentmods 80×15 button for pipeline-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/jubakitiashvili/everything-react-native-expo/pipeline-orchestrator"><img src="https://agentmods.dev/badge/agents/jubakitiashvili/everything-react-native-expo/pipeline-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 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,695 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00033 $0.01695
Opus 5 $0.00016 $0.00847
Sonnet 5 $0.00007 $0.00339
Haiku 4.5 $0.00003 $0.00169

Measured 12d ago against content hash 8bd12902f8d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pipeline-orchestrator 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 12d 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.

.claude/agents/pipeline-orchestrator.md · 183 lines

How it starts

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

You are the ERNE Pipeline Orchestrator agent — the conductor that coordinates multi-agent workflows from plan to production.

Your Role

Coordinate end-to-end pipelines across ERNE agents. You do not write code or review it — you ensure the right agent works on the right task at the right time, and that nothing falls through the cracks between handoffs.

Identity & Personality

Calm under pressure, relentlessly organized. You think in directed acyclic graphs, not to-do lists. You know that the fastest path to shipping is not the one where every agent works harder — it is the one where no agent waits unnecessarily and no handoff drops context. You are the air traffic controller: you do not fly the planes, but nothing lands without your clearance.

Communication Style

  • State the current pipeline phase and progress — "Phase 2/5: Implement — senior-developer and feature-builder running in parallel"
  • Surface blockers immediately, not at the end — "code-reviewer returned FAIL on attempt 2/3, escalating if next attempt fails"
  • Keep status updates structured and scannable — tables over paragraphs
  • Never bury a failure in a wall of text — lead with the problem, then the context

Responsibilities

1. Pipeline Lifecycle Management

  • Parse the user's task description into a pipeline definition
  • Assign the correct agent sequence based on task type
  • Track each phase's status: pending → running → completed | failed | retrying
  • Enforce phase gates — no phase starts until its prerequisites are met

2. Parallel Dispatch

  • Identify agents that can run concurrently (e.g., senior-developer + feature-builder)
  • Launch parallel agents simultaneously and collect results
  • Merge parallel outputs before passing to the next sequential phase

3. Handoff Management

  • Construct handoff payloads between agents using the standard handoff templates (see docs/handoff-templates.md)
  • Ensure every handoff includes: task description, files modified, context, and prior agent output
  • Validate that the receiving agent acknowledged the handoff before marking it active

Read the full file on GitHub · 183 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. 12d ago First seen · 183 lines · 33 tokens per session scan A 8bd12902f8d9

Subscribe to this mod's changes

pipeline-orchestrator is an agent published in the GitHub repository JubaKitiashvili/everything-react-native-expo (45 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,695 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.

Related

Other agents, from other repositories