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/tatargabor/set-copilot/loopgit clone --depth 1 https://github.com/tatargabor/set-copilotWrote 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/tatargabor/set-copilot/loop)<a href="https://agentmods.dev/commands/tatargabor/set-copilot/loop"><img src="https://agentmods.dev/badge/commands/tatargabor/set-copilot/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.00000 | $0.00537 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
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 today.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Ralph Loop
Start an autonomous Ralph loop for the given change-id and task.
Arguments: <change-id> "<task description>" [--max N] [--done criteria]
Instructions
Start the Ralph loop and then monitor its progress until completion.
Step 1: Start the loop
set-loop start $ARGUMENTS
Step 2: Monitor progress
After starting, run the monitor command to track progress until the loop completes:
set-loop monitor <change-id> --interval 30
This will output iteration updates and report the final status (done/stuck/stopped).
Options
--max N- Maximum iterations (default: 10)--done criteria- Done detection:tasks,openspec, ormanual(default: tasks, auto-detects openspec)--capacity-limit PCT- Stop if capacity exceeds threshold (default: 80%)--stall-threshold N- Stall after N commit-less iterations (default: 2)--iteration-timeout N- Per-iteration timeout in minutes (default: 45)--permission-mode MODE- Claude permission mode:auto-accept,allowedTools,plan(default: config)--label TEXT- Label for this loop instance (shown in banner and terminal title)--force- Force start even with incompatible permission mode (e.g. plan)
Examples
# Basic usage - implement feature per tasks.md
set-loop start add-auth "Implement authentication per spec"
# With options
set-loop start add-api "Build REST API endpoints" --max 15 --done tasks
# Manual done criteria (you mark it done)
set-loop start refactor "Refactor UserService" --done manual
What happens
- A new terminal window opens with the Ralph loop
- Claude Code runs iteratively on the task
- After each iteration, checks if tasks.md is complete
- Loop ends when done criteria met OR max iterations reached
- Notification sent when complete or stuck
- The monitor command reports progress back to you
Manual commands
set-loop status <change-id> # Check current status
set-loop list # List all active loops
set-loop stop <change-id> # Stop a running loop
set-loop history <change-id> # View iteration history
set-loop monitor <change-id> # Monitor until complete
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.
- today First seen · 69 lines · 0 tokens per session scan A d14af5328155
loop is a command published in the GitHub repository tatargabor/set-copilot (2 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 537 tokens. 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-09-04.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.