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.
curl -O https://raw.githubusercontent.com/JubaKitiashvili/everything-react-native-expo/main/.claude/skills/erne-orchestrate/SKILL.mdgit clone --depth 1 https://github.com/JubaKitiashvili/everything-react-native-expoWrote 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/skills/jubakitiashvili/everything-react-native-expo/erne-orchestrate)<a href="https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/erne-orchestrate"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/erne-orchestrate/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/skills/jubakitiashvili/everything-react-native-expo/erne-orchestrate"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/erne-orchestrate.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.00025 | $0.01054 |
| Opus 5 | $0.00013 | $0.00527 |
| Sonnet 5 | $0.00005 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
erne-orchestrate 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- orchestrate — 95% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/erne-orchestrate — Multi-Agent Pipeline Execution
You are executing the /erne-orchestrate command. Use the pipeline-orchestrator agent to coordinate a full pipeline across multiple ERNE agents.
Usage
/orchestrate "build user profile screen"
/orchestrate "add pull-to-refresh to the feed"
/orchestrate "implement dark mode toggle"
Pipeline Definition
The standard pipeline runs 5 phases with the following agent sequence:
Phase 1: Plan (Sequential)
Agent: architect
- Decompose the task into an architecture plan
- Define file structure, component hierarchy, data flow, and navigation
- Output: Architecture document with numbered implementation tasks
- Gate: Architecture plan produced and confirmed
Phase 2: Implement (Parallel)
Agents: senior-developer + feature-builder (running simultaneously)
- senior-developer: Implements screens, hooks, API integration, state management
- feature-builder: Implements supporting components, utilities, and wiring
- Work is split by the architect's task breakdown — non-overlapping file ownership
- Output: Complete implementation across all specified files
- Gate: All implementation tasks marked complete, code compiles
Phase 3: Test (Sequential)
Agent: tdd-guide
- Write unit tests for new hooks and utilities
- Write component tests for new screens
- Run the test suite and ensure all tests pass
- Output: Test files and passing test results
- Gate: All tests written and passing
Phase 4: Review (Sequential)
Agent: code-reviewer
- Review all new and modified files
- Check for re-render issues, anti-patterns, platform parity, accessibility, security
- Verdict: PASS, FAIL, or RETRY
- PASS: Proceed to Phase 5
- FAIL: Send QA FAIL handoff back to Phase 2 agents with required fixes (up to 3 attempts)
- RETRY: Minor issues that can be auto-fixed, then re-review
- Gate: PASS verdict from code-reviewer
Phase 5: Validate (Sequential)
Agent: performance-profiler
- Measure rendering performance, bundle size impact, and memory usage
- Verify all metrics are within project targets
- Output: Performance report with metrics table
- Gate: All performance metrics within acceptable ranges
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.
- 11d ago First seen · 116 lines · 25 tokens per session scan A 03e61c4bd670
erne-orchestrate is a skill published in the GitHub repository JubaKitiashvili/everything-react-native-expo (45 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 1,054 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…