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 agentmods add commands/vcz-gray/loophaus/ralph-loopgit 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/commands/vcz-gray/loophaus/ralph-loop)<a href="https://agentmods.dev/commands/vcz-gray/loophaus/ralph-loop"><img src="https://agentmods.dev/badge/commands/vcz-gray/loophaus/ralph-loop.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00489 |
| Opus 5 | $0.00008 | $0.00244 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
ralph-loop 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 4d 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.
What it actually says
Ralph Loop Command
You are about to start a Ralph Loop. Parse the user's arguments as follows:
Argument Parsing
- Extract
--max-iterations N(default: 20). Must be a positive integer or 0 (unlimited). - Extract
--completion-promise TEXT(default: "TADA"). Multi-word values must be quoted. - Everything else is the prompt — the task description.
Setup
Run this command to initialize the Ralph loop state file:
node -e "
import { writeState } from '${RALPH_CODEX_ROOT}/store/state-store.mjs';
await writeState({
active: true,
prompt: PROMPT_HERE,
completionPromise: PROMISE_HERE,
maxIterations: MAX_HERE,
currentIteration: 0,
sessionId: ''
});
"
Replace PROMPT_HERE, PROMISE_HERE, and MAX_HERE with the parsed values. Use proper JSON string escaping for the prompt.
Alternatively, create the state file directly at .codex/ralph-loop.state.json:
{
"active": true,
"prompt": "<user's prompt>",
"completionPromise": "<promise text>",
"maxIterations": 20,
"currentIteration": 0,
"sessionId": ""
}
After Setup
Display this message to the user:
Ralph loop activated!
Iteration: 1
Max iterations: <N or "unlimited">
Completion promise: <promise text>
The stop hook will now block session exit and feed the SAME PROMPT back.
Your previous work persists in files and git history.
To cancel: /cancel-ralph
Then immediately begin working on the user's task prompt.
Rules
- When a completion promise is set, you may ONLY output
<promise>TEXT</promise>when the statement is genuinely and completely TRUE. - Do NOT output false promises to exit the loop.
- Each iteration sees your previous work in files. Build on it incrementally.
- If stuck, document what's blocking and try a different approach.
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.
- 4d ago First seen · 74 lines · 16 tokens per session scan A 388d4d74615b
ralph-loop is a command published in the GitHub repository vcz-Gray/loophaus (23 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 489 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.