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.
Borrowing it
Nothing to install: this file belongs to mikeyobrien/ralph-orchestrator. 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/mikeyobrien/ralph-orchestrator/main/.claude/skills/code-assist/SKILL.mdgit 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/code-assist)<a href="https://agentmods.dev/skills/mikeyobrien/ralph-orchestrator/code-assist"><img src="https://agentmods.dev/badge/skills/mikeyobrien/ralph-orchestrator/code-assist/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/mikeyobrien/ralph-orchestrator/code-assist"><img src="https://agentmods.dev/badge/skills/mikeyobrien/ralph-orchestrator/code-assist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.02029 |
| Opus 5.5 | $0.00021 | $0.00812 |
| Sonnet 5.5 | $0.00011 | $0.00406 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade A, and why
code-assist 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Assist
Overview
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Balances automation with user collaboration while adhering to existing package patterns and prioritizing readability and extensibility.
Parameters
- task_description (required): Task specification, rough idea, file path to
.code-task.md, or URL - additional_context (optional): Supplementary information for implementation context
- documentation_dir (optional, default: ".sop/planning"): Directory for planning documents
- repo_root (optional, default: current working directory): Repository root for code implementation
- task_name (optional): Short descriptive name (auto-generated if not provided)
- mode (optional, default: "auto"): "interactive" (confirmation at each step) or "auto" (autonomous execution)
Constraints:
- You MUST ask for all parameters upfront in a single prompt to avoid repeated interruptions
- You MUST validate inputs: normalize mode to "interactive"/"auto", verify paths, generate task_name if needed
Mode Behavior
Apply these patterns throughout all steps:
Interactive Mode: Present actions for confirmation. Explain pros/cons when multiple approaches exist. Ask clarifying questions. Pause at key decision points. Provide educational context.
Auto Mode: Execute autonomously. Document all decisions and reasoning in progress.md. Select the most appropriate approach and document why. Provide comprehensive summaries at completion.
Important Notes
Separation of Concerns:
Documentation goes in {documentation_dir}. Code (tests and implementation) goes in repo_root. Never mix them. Documentation should guide implementation with high-level concepts — not provide it. When including code snippets in documentation, keep them brief and clearly label them as examples or references.
CODEASSIST.md Integration: If CODEASSIST.md exists in repo_root, read it and apply its constraints throughout.
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.
- 1mo ago First seen · 217 lines · 53 tokens per session scan A 519fc4a01023
code-assist is a skill published in the GitHub repository mikeyobrien/ralph-orchestrator (3,186 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 2,029 once invoked, about $0.0002 per session on Opus 5.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
test-generation
Use when the user asks for tests, mentions TDD, or when new code has been written and needs test coverage.
tdd-patterns
Guide test-driven development through the mandatory Red-Green-Refactor cycle: a test is RED only when it fails for the intended reason, its expected value has a stated source (spec, reference implementation, hand computation, fixture, or standard — never the implementation's own output), and its input discriminates…
tdd
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate.
implement_task
Implementation agent that executes a single task and creates handoff on completion.
tdd-migration-pipeline
Orchestrator-only workflow for migrating/rewriting codebases with full TDD and agent delegation.
bats-testing-patterns
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.