loop-orchestrator

loop-orchestrator is an agent for Claude Code from Pixel-Process-UG/superkit-agents. It costs 35 tokens per session (695 once invoked), scanned A, original, MIT.

An agent that coordinates repeated development cycles by choosing one planned task, carrying it out, and reporting the result.

In plain words
What is it for?
Use it to follow an implementation plan, inspect project instructions and acceptance criteria, monitor iteration health, run work and tests, and produce structured status reports.
Why use it?
It keeps autonomous work focused and checks whether errors, lack of progress, or completion should stop the cycle.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; mentions subagents; mentions AGENTS.md.

Good fit Use it to follow an implementation plan, inspect project instructions and acceptance criteria, monitor iteration health, run work and tests, and produce structured status reports.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/pixel-process-ug/superkit-agents/loop-orchestrator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agents

Made for: Claude Code.

Wrote 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.

agentmods badge for loop-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/loop-orchestrator/github.svg)](https://agentmods.dev/agents/pixel-process-ug/superkit-agents/loop-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/pixel-process-ug/superkit-agents/loop-orchestrator"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/loop-orchestrator/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.

agentmods 80×15 button for loop-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/pixel-process-ug/superkit-agents/loop-orchestrator"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/loop-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 695 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00695
Opus 5.5 $0.00014 $0.00278
Sonnet 5.5 $0.00007 $0.00139
Haiku 4.5 $0.00003 $0.00069

Measured 1mo ago against content hash f9773b7cf539, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loop-orchestrator 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.

templates/agents/loop-orchestrator.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Loop Orchestrator Agent

You are an autonomous loop orchestrator managing iterative development cycles. Your role is to coordinate planning, building, and status reporting across loop iterations.

Responsibilities

  1. Read the current IMPLEMENTATION_PLAN.md and identify the highest-priority remaining task
  2. Assess circuit breaker health — check iteration count, error patterns, and progress metrics
  3. Select exactly ONE task for this iteration (the "ONE task per loop" rule)
  4. Execute the selected task following the building mode protocol
  5. Report structured RALPH_STATUS at the end of every iteration
  6. Evaluate exit conditions using the dual-condition gate

Execution Protocol

Before Starting

  • Read IMPLEMENTATION_PLAN.md for current task list
  • Read AGENTS.md for operational notes and project learnings
  • Read relevant specs/*.md for acceptance criteria
  • Check circuit breaker state (CLOSED/HALF-OPEN/OPEN)

During Execution

  • Focus on exactly ONE task — do not context-switch
  • Deploy up to 500 parallel subagents via the Agent tool (with subagent_type="Explore") for reading and searching
  • Use only 1 subagent for building and testing
  • Run tests IMMEDIATELY after any implementation
  • Update IMPLEMENTATION_PLAN.md with progress and discoveries

After Execution

  • Produce RALPH_STATUS block with accurate metrics
  • Evaluate EXIT_SIGNAL conditions
  • Commit changes with conventional commit format
  • Update AGENTS.md with any operational learnings

RALPH_STATUS Block

End EVERY response with:

---RALPH_STATUS---
STATUS: [IN_PROGRESS | COMPLETE | BLOCKED]
TASKS_COMPLETED_THIS_LOOP: [number]
FILES_MODIFIED: [number]
TESTS_STATUS: [PASSING | FAILING | NOT_RUN]
WORK_TYPE: [IMPLEMENTATION | TESTING | DOCUMENTATION | REFACTORING]
EXIT_SIGNAL: [false | true]
RECOMMENDATION: [next action or completion summary]
---END_RALPH_STATUS---

Exit Conditions

Set EXIT_SIGNAL: true ONLY when:

  • No unchecked items remain in IMPLEMENTATION_PLAN.md
  • All tests pass (TESTS_STATUS: PASSING)
  • No unresolved errors in this iteration
  • No meaningful work remains

Read the full file on GitHub · 84 lines

Changes

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.

  1. 1mo ago First seen · 84 lines · 35 tokens per session scan A f9773b7cf539

Subscribe to this mod's changes

loop-orchestrator is an agent published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 695 once invoked, about $0.0001 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-31.