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.
npx skills add vcz-Gray/loophaus --skill ralph-orchestratorgit clone --depth 1 https://github.com/vcz-Gray/loophausWrote 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/vcz-gray/loophaus/ralph-orchestrator)<a href="https://agentmods.dev/skills/vcz-gray/loophaus/ralph-orchestrator"><img src="https://agentmods.dev/badge/skills/vcz-gray/loophaus/ralph-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.
<a href="https://agentmods.dev/skills/vcz-gray/loophaus/ralph-orchestrator"><img src="https://agentmods.dev/badge/skills/vcz-gray/loophaus/ralph-orchestrator.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.00024 | $0.02096 |
| Opus 5 | $0.00012 | $0.01048 |
| Sonnet 5 | $0.00005 | $0.00419 |
| Haiku 4.5 | $0.00002 | $0.00210 |
Grade B, and why
ralph-orchestrator scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
# Enable in ~/.codex/config.toml How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loop Orchestrator — Multi-Agent Loop Patterns
You are an expert at designing optimal execution strategies for Loop tasks. When asked to orchestrate a task, analyze its structure and recommend the best combination of sequential loops, parallel subagents, and phased execution.
Core Concept
Not every task should run in a single linear loop. Complex tasks benefit from:
- Parallel exploration — spawn subagents to search/analyze independently, then merge results
- Divide and conquer — split work by service/directory/concern with isolated agents
- Pipeline stages — sequential phases where each feeds into the next
- Hybrid patterns — combine parallel research with sequential implementation
When to Use Subagents
Use Subagents (Parallel) When:
| Signal | Example |
|---|---|
| Broad codebase search | "Find all API endpoints that lack auth checks" |
| Independent file groups | Frontend components + backend routes + database migrations |
| Multi-service changes | auth-service + api-gateway + frontend simultaneously |
| Audit/review tasks | Security audit + performance audit + accessibility audit |
| Pattern extraction | Scan 50+ files for inconsistent patterns |
Do NOT Use Subagents When:
| Signal | Reason |
|---|---|
| Sequential dependencies | Step 2 needs Step 1's output |
| Shared mutable state | Multiple agents editing the same file = conflicts |
| Small scope (< 5 files) | Overhead outweighs benefit |
| Context-heavy tasks | Agent needs deep understanding of full codebase flow |
Orchestration Patterns
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 · 255 lines · 24 tokens per session scan B 711f95fac285
ralph-orchestrator is a skill published in the GitHub repository vcz-Gray/loophaus (23 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 2,096 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…