Ralph Orchestrator is a framework that repeatedly runs AI-agent tasks until they finish or reach an iteration limit. Developers use it to coordinate autonomous coding work through command-line, web-dashboard, and MCP-server interfaces, with state managed per workspace. The catalogue entries provide agent skills, agents, instructions, and plugins for operating Ralph.
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 mikeyobrien/ralph-orchestrator --skill ralph-docsgit clone --depth 1 https://github.com/mikeyobrien/ralph-orchestratorWrote 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/mikeyobrien/ralph-orchestrator/ralph-docs)<a href="https://agentmods.dev/skills/mikeyobrien/ralph-orchestrator/ralph-docs"><img src="https://agentmods.dev/badge/skills/mikeyobrien/ralph-orchestrator/ralph-docs.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 59 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00117 | $0.01438 |
| Opus 5 | $0.00059 | $0.00719 |
| Sonnet 5 | $0.00023 | $0.00288 |
| Haiku 4.5 | $0.00012 | $0.00144 |
Grade A, and why
ralph-docs scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sSfL https://mikeyobrien.github.io/ralph-orchestrator/llms.txt \ How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph Docs
Introspect Ralph Orchestrator the same way the framework expects a smart agent to — consult the published documentation map at https://mikeyobrien.github.io/ralph-orchestrator/llms.txt, fetch only the sections relevant to the question, and answer from authoritative sources.
Use this skill to behave like an internal Ralph contributor rather than a guess-first assistant.
Use This Skill For
- Answering "how does Ralph do X?" questions about the event loop, hats, memories, tasks, presets, backends, CLI, TUI, diagnostics, waves, or API.
- Explaining an observed behavior ("why did my loop terminate with max_iterations?", "why didn't my hat fire?") from first principles in the docs, not pattern-matching.
- Proposing and scoping an improvement to the
ralph-orchestratorcodebase — locating the right crate, the relevant concept doc, and the existing test surface before writing code. - Triaging a ralph bug report: map symptoms to likely subsystem, pull in the concept + reference docs for that subsystem, identify the probable file path in the repo.
- Onboarding: answer a new user's setup/quick-start questions from the official Getting Started pages instead of the agent's stale training data.
Core Principle: llms.txt Is The Router
Ralph's llms.txt is a curated map, not a full-text dump. The workflow is:
- Discover — fetch
llms.txtto see the top-level sections (Getting Started / Concepts / User Guide / Advanced / API / Examples / Contributing / Reference). - Narrow — pick the 1–3 pages that actually answer the question. The map
links directly to
.mdversions — those are agent-optimized and should be preferred over scraping HTML. - Fetch — pull only those pages. Do not fetch more than three pages speculatively; the budget should be spent on answering, not browsing.
- Cross-check — for code-level claims, confirm against the repo (crate paths are listed in AGENTS.md / CLAUDE.md inside the ralph-orchestrator checkout).
- Answer — cite the page you relied on. Include the URL so the user can verify.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 118 lines · 117 tokens per session scan A 833a031ca31c
ralph-docs is a skill published in the GitHub repository mikeyobrien/ralph-orchestrator (3,127 stars, last pushed 6d ago), licensed MIT. It adds 117 tokens to every session and 1,438 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
chart
Use when the user asks to visualize data with charts, graphs, or plots using the chart tool (bar, line, scatter, pie, time series, etc.).
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
nx-workspace
Run and generate NX targets, configure project.json, and visualize dependency graphs. Use when you say: 'run affected tests', 'nx generate a library', 'configure project.json', or 'show dependency graph'.
playwright-testing
Playwright E2E testing patterns, cross-browser configuration, page objects, and CI setup. Use when creating E2E specs, visual regression suites, or configuring Playwright in CI. Trigger terms: playwright, e2e, trace, page object, cross-browser.
agent-memory
Creates, queries agent expertise profiles in AGENT-EXPERTISE.md; increments file-familiarity counters after each task; ranks candidate agents by recency, task-area match. Use when deciding which agent should handle a file, checking who last worked on a module, recording task outcomes, or assigning work based on past…
data-engineering
Transforms, validates, loads data in ETL pipelines. Use when building scrapers, validating NDJSON feeds, or importing data into CMS/DB targets.