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/tui-validate/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/tui-validate)<a href="https://agentmods.dev/skills/mikeyobrien/ralph-orchestrator/tui-validate"><img src="https://agentmods.dev/badge/skills/mikeyobrien/ralph-orchestrator/tui-validate/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/tui-validate"><img src="https://agentmods.dev/badge/skills/mikeyobrien/ralph-orchestrator/tui-validate.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.00044 | $0.02931 |
| Opus 5 | $0.00022 | $0.01465 |
| Sonnet 5 | $0.00009 | $0.00586 |
| Haiku 4.5 | $0.00004 | $0.00293 |
Grade A, and why
tui-validate 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 9d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TUI Validate
Overview
This skill validates Terminal User Interface (TUI) applications by capturing their output and using LLM-as-judge for semantic validation. It leverages freeze from Charmbracelet for high-fidelity terminal screenshots and provides structured validation criteria.
Philosophy: Rather than brittle string matching, this skill uses semantic understanding to validate that TUI output "looks right" - checking layout, content presence, and visual hierarchy without breaking on minor formatting changes.
When to Use
- Validating TUI rendering after changes
- Checking that UI components display correctly
- Visual regression testing for terminal applications
- Verifying TUI state after specific interactions
- Creating documentation screenshots with validation
Prerequisites
Required:
freezeCLI tool installed (brew install charmbracelet/tap/freeze)tmuxfor interactive TUI capture (optional, for live applications)
Verification:
# Check freeze is installed
freeze --version
# Check tmux is installed (for interactive capture)
tmux -V
Parameters
-
target (required): What to validate. One of:
file:<path>- ANSI output file to validatecommand:<cmd>- Command to execute and capturetmux:<session>- Live tmux session to capturebuffer:<text>- Raw text/ANSI to validate
-
criteria (required): Validation criteria. Can be:
- A predefined criteria name (see Built-in Criteria)
- A custom criteria string describing what to check
-
output_format (optional, default: "svg"): Screenshot format
svg- Vector format, best for documentationpng- Raster format, best for visual difftext- Text-only extraction, fastest
-
save_screenshot (optional, default: false): Whether to save the screenshot
- If true, saves to
{target_name}.{format}in current directory
- If true, saves to
-
judge_mode (optional, default: "semantic"): Validation approach
semantic- LLM judges based on meaning and layoutstrict- Also checks exact content presencevisual- Requires PNG, checks visual appearance
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.
- 9d ago First seen · 439 lines · 44 tokens per session scan A c490d51a521b
tui-validate is a skill published in the GitHub repository mikeyobrien/ralph-orchestrator (3,127 stars, last pushed 7d ago), licensed MIT. It adds 44 tokens to every session and 2,931 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.
Other skills, from other repositories
vscode-visual-regression
Write Storybook stories and visual regression tests for the Kilo VS Code extension webview UI.
test-generation
Use when the user asks for tests, mentions TDD, or when new code has been written and needs test coverage.
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.
vitest-testing
Vitest unit and integration testing patterns, commands, mocking (vi.mock), and coverage. Use when writing .test.ts files, configuring the test runner, or adding coverage thresholds.
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.
cypress-testing
Writes Cypress E2E/component tests, configures cy.intercept() and cy.session(), authors custom commands, and wires CI artifacts. Use when creating E2E specs, component tests, or CI test pipelines. Trigger terms: cypress, e2e, component test, cy.intercept, cy.session.