ralph-claude-orchestrator

ralph-claude-orchestrator is a skill for Claude Code from vcz-Gray/loophaus. It costs 30 tokens per session (994 once invoked), scanned A, original, MIT.

A collection of multi-agent work patterns for Claude Code, a coding environment that can use separate AI agents to work on tasks. It describes when to run agents in parallel or in sequence and how to isolate their file changes.

In plain words
What is it for?
Use it to plan parallel codebase exploration, divide frontend and backend investigations, run staged implementation workflows, and choose agent roles and worktree isolation for Claude Code tasks.
Why use it?
It helps organize large tasks that benefit from multiple independent scans or implementations. Isolation can keep agents’ changes separate, while sequential steps let later work use earlier findings.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code.

Part of the loophaus plugin — 6 skills, 7 commands, 1 hook shipped together

Good fit Use it to plan parallel codebase exploration, divide frontend and backend investigations, run staged implementation workflows, and choose agent roles and worktree isolation for Claude Code tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vcz-gray/loophaus/ralph-claude-orchestrator
Install

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.

Any agent
npx skills add vcz-Gray/loophaus --skill ralph-claude-orchestrator
Clone the repo
git clone --depth 1 https://github.com/vcz-Gray/loophaus

Made for: Claude Code.

Or install loophaus, the plugin that ships this one along with the rest of its 6 skills, 7 commands, 1 hook.

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 ralph-claude-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/vcz-gray/loophaus/ralph-claude-orchestrator/github.svg)](https://agentmods.dev/skills/vcz-gray/loophaus/ralph-claude-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/vcz-gray/loophaus/ralph-claude-orchestrator"><img src="https://agentmods.dev/badge/skills/vcz-gray/loophaus/ralph-claude-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 ralph-claude-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/vcz-gray/loophaus/ralph-claude-orchestrator"><img src="https://agentmods.dev/badge/skills/vcz-gray/loophaus/ralph-claude-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 994 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.00030 $0.00994
Opus 5 $0.00015 $0.00497
Sonnet 5 $0.00006 $0.00199
Haiku 4.5 $0.00003 $0.00099

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

Security

Grade A, and why

ralph-claude-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.

skills/ralph-claude-orchestrator/SKILL.md · 130 lines

How it starts

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

Loop Orchestrator — Multi-Agent Patterns (Claude Code)

Orchestration patterns optimized for Claude Code's Agent tool. Analyzes tasks and recommends the best combination of sequential loops and parallel subagents.

Subagent Configuration (Claude Code Agent Tool)

Agent tool parameters:
- description: "short task description"
- prompt: "detailed instructions"
- subagent_type: "general-purpose" | "Explore" | "Plan" | "coder-fe" | "coder-be"
- isolation: "worktree"  (gives agent an isolated repo copy)
- run_in_background: true  (for parallel execution)

Best practices:

  • Use subagent_type: "Explore" for read-only scanning — faster and safer
  • Use isolation: "worktree" when agents write to files — prevents merge conflicts
  • Launch parallel agents in a single message with multiple Agent tool calls
  • Use run_in_background: true for truly independent work streams

Orchestration Patterns

Pattern 1: Parallel Explore then Sequential Implement

Best for: Large codebases where you need to understand before you change.

Phase 1 (Parallel Subagents via Agent tool):
├── Agent "fe-scan" (Explore, background): Scan src/frontend/** → .loophaus/reports/frontend.md
├── Agent "be-scan" (Explore, background): Scan src/backend/** → .loophaus/reports/backend.md
└── Agent "db-scan" (Explore, background): Scan src/db/** → .loophaus/reports/db.md

Phase 2 (Loop):
└── Read merged reports → implement fixes story by story via prd.json

Pattern 2: Divide by Ownership

Best for: Multi-service changes where files do not overlap.

Spawn agents with isolation: "worktree":
├── Agent "fe-dev" (worktree): ONLY touch src/frontend/** → commit per item
├── Agent "be-dev" (worktree): ONLY touch src/backend/** → commit per item
└── Agent "auth-dev" (worktree): ONLY touch src/auth/** → commit per item

After all complete: merge branches, run integration tests

Pattern 3: Fan-Out / Fan-In Research

Best for: Comprehensive analysis before any action.

Fan-Out (parallel Agent calls in single message):
├── Agent "security" (Explore): Audit for OWASP top 10 → findings.md
├── Agent "perf" (Explore): Profile and benchmark → findings.md
└── Agent "a11y" (Explore): Check accessibility → findings.md

Fan-In (Loop):
└── Synthesize all findings → create action plan → implement

Read the full file on GitHub · 130 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 · 130 lines · 30 tokens per session scan A 7ea2c87c1c8b

Subscribe to this mod's changes

ralph-claude-orchestrator is a skill published in the GitHub repository vcz-Gray/loophaus (23 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 994 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 skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens