Which AI agents does this loop work with?

Content operations monitor via custom loop.md is written for claude-code.

Is this loop safe to run unattended?

This loop is graded C (65/100) by looprepo's automatic safety evaluator, which checks for exit conditions, iteration budgets, verification steps, and scoping before publishing.

Loop/loop Automationmedium riskintermediatesafety C · 65 community

Content operations monitor via custom loop.md

A marketing-facing loop.md playbook that turns a bare /loop into a recurring content-ops sweep: checks GA4 for week-over-week organic traffic drops, scans GSC for position 4-15 query opportunities, and audits WordPress posts for broken internal links and missing meta descriptions — reporting one line when everything is green.

prompt

→ Claude Code

/loop 15m (Save the following as .claude/loop.md so the bare /loop picks it up as its playbook.) # .claude/loop.md — Content Operations Monitor Check the following every iteration: 1. Pull the latest GA4 data for kokasexton.com. If any post dropped more than 30% in organic traffic week-over-week, flag it with the URL and the percentage drop. 2. Scan GSC for new queries where we rank positions 4-15 and impressions grew >20% week-over-week. List the top 3 opportunities. 3. Check the WordPress admin for any posts with broken internal links or missing meta descriptions. Fix silently if fewer than 5 issues. Report if more. 4. If everything is green, reply with one line: "Content ops clean — nothing needs attention." Cap the run at 15 passes.

claude-code

Implementation note

Requires GA4/GSC/WordPress access via MCP connectors before it can do anything useful — without them the loop will hallucinate or no-op. Step 3 lets the agent fix issues silently below a threshold; run with a scoped WordPress account and review the first few iterations before trusting silent fixes. Replace kokasexton.com with your own property. Loops expire after 7 days by default in Claude Code, which caps runaway cost.

Source: Koka Sexton ↗graded C · 65/100 — how grades work →

More automation loops

Ship PRD stories via dual-agent loop

Loop/ralphGitHub A

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/ralphGitHub B

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/goalGitHub B

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 ↗