Loop/ralphAutomationmedium riskintermediatesafety C · 55 · open-endedGitHub

claude-loop — iterative sessions with cost tracking

An automation harness that runs repeated Claude Code sessions while tracking cost and tokens per iteration — the reference answer to the number-one objection to agent loops: runaway spend.

prompt
→ Claude Code
Automation toolkit running repeated `claude` sessions with per-iteration cost and token monitoring; inspired by Dex Horthy's context-engineering talk. Cap the run at 25 iterations; leave remaining work for the next session.
claude-code

Implementation note

When to use: you are sold on iterative agent sessions but not on surprise bills — this harness exists specifically to answer the number-one objection to agent loops, runaway spend. Inspired by Dex Horthy's context-engineering talk. How it works: an automation toolkit that runs repeated claude sessions in a loop while recording cost and token usage per iteration, so you can see exactly what each cycle consumed rather than discovering the total afterward. The per-iteration granularity is what makes the data actionable: an iteration whose token count spikes is visible immediately, and trends across a run tell you whether the loop is converging or thrashing. Safety: measurement is the rail here — per-iteration cost visibility is what lets you set informed caps and kill a run that is trending wrong. Pair it with hard limits (iteration caps, budget ceilings), since tracking alone observes spend rather than stopping it.

Source: li0nel/claude-loop ↗graded C · 55/100 — how grades work →

More automation loops

Ship PRD stories via dual-agent loop

Loop/ralphGitHubA

Ralph runs a generator and evaluator in tandem until all user stories pass acceptance criteria and browser tests.

prompt
→ Claude Code
# Ralph Harness — Agent Instructions ## Overview Ralph Harness is an autonomous AI agent loop that runs AI coding tools (Amp or Claude Code) repeatedly until all PRD items are complete. Each iteration is a fresh instance with clean context. Ralph supports two modes: | Mode | Architecture | When to use | |------|-------------|-------------| | simple | Single agent (self-implement, self-check) | Quick tasks, backend-only stories, well-defined small changes | | harness | Generator + Evaluator (dual-agent with contract) | UI-heavy features, complex stories, when quality is critical | ## Architecture: Harness Mode ralph.sh orchestrator │ ├── Planner (prd.json) │ Defines user stories, acceptance criteria, dependencies │ ├── Generator (generator-prompt.md) │ Drafts sprint contracts → Implements stories → Fixes based on feedback │ └── Evaluator (evaluator-prompt.md) Reviews contracts → Signs/locks → Tests in browser → Scores → Writes feedback ### Per-Story Flow 1. Contract Negotiation : Generator drafts contract.json → Evaluator reviews → Back-and-forth until Evaluator signs → Contract locked (immutable) 2. Build : Generator reads Hard cap: stop after 30 iterations even if PRD items remain.
automationhigh risk
claude-code
m18897829375 ↗

Ship production-grade apps autonomously

Loop/ralphGitHubB

Hand an idea to Claude Code; it authors specs, designs, builds, tests, secures, and ships until enterprise done or budget exhausted.

prompt
→ Claude Code
# dare-to-be-stupid — Design (v2, refined) > A Claude Code plugin. One command, /dare , hands an idea or PRD to an autonomous > loop that authors specs, designs, builds, tests, secures, ships, fixes, and iterates > until the app passes an enterprise-production definition of done — or the budget dies. > > Named for the Weird Al song. The joke is that it runs the Ralph Loop on purpose , > with --dangerously-skip-permissions , and narrates the whole thing in the voice of an > '80s Junkion. Pre-production only. Never points at anything with users. This is v2. It keeps the strong core of the original spec (external reviewer, ratchet, guard hook, Junkion style) and adds the three phases the original left thin relative to the actual goal: PRD authoring, a design phase, and a real enterprise DoD including security, CI, docs/observability, and design quality (with quality plugins auto-installed). --- ## 0. The premise, in one paragraph The User builds documentation-first: spec → system docs → API contracts → CLAUDE.md → code. dare-to-be-stupid is the deliberate inverse, packaged as comedy that also solves two real engineering problems. It is a real build , not a joke ar
automationhigh risk
claude-code
trevor-ryan-burkholder ↗

Set and ship autonomous goals

Loop/goalGitHubB

Run a persistent goal autonomously until completion, routing each task to the optimal model for cost and capability.

prompt
→ Claude Code
/goal <objective · /loop <task | Set a persistent goal · run autonomously until complete (≤25 turns) |
automationlow risk
claude-code
adulari ↗