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.
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/loop)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/loop"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.1 | $0.00016 | $0.01085 |
| Opus 5 | $0.00008 | $0.00543 |
| Sonnet 5 | $0.00003 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/loop — Bounded Repetitive Task Execution
Run a task across multiple targets (files, modules, endpoints, etc.) with safety bounds, progress tracking, and stall detection.
Flags
| Flag | Default | Description |
|---|---|---|
--targets |
(required) | Comma-separated list or glob pattern of targets |
--parallel |
false | Run iterations concurrently (use with caution) |
--max |
10 | Maximum number of iterations (safety bound) |
--continue-on-error |
false | Continue to next target if one fails |
Instructions
Step 1: Parse Arguments
From $ARGUMENTS, extract:
- Task description: What to do to each target
- Targets: List of files, modules, or items to iterate over
- Execution mode: Sequential (default) or parallel
- Max iterations: Safety cap (default: 10)
- Error handling: Stop on first error (default) or continue
Step 2: Resolve Targets
If targets are a glob pattern, resolve them:
# Resolve glob to file list
ls [glob-pattern] 2>/dev/null
If targets are a comma-separated list, split them.
Validate:
- Target count must be > 0 (error if empty)
- Target count must be <= max iterations (warn and cap if exceeded)
- Each target must exist (if file-based)
Step 3: Initialize State
Create .planning/loop-state.json:
{
"task": "[description]",
"mode": "sequential|parallel",
"max_iterations": 10,
"targets": ["target1", "target2"],
"status": "running",
"started": "[ISO timestamp]",
"iterations": [],
"stall_count": 0
}
Step 4: Pre-Loop Baseline
# Capture baseline test status
npm test 2>&1 | tail -5
git status --short
Record baseline state for stall detection.
Step 5: Execute Loop
For each target (sequential or parallel based on mode):
-
Announce: "Iteration [N]/[total]: Processing [target]"
-
Execute the task on the current target
-
Verify iteration:
# Run tests after each iteration
npm test 2>&1 | tail -5
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.
- 8d ago First seen · 167 lines · 16 tokens per session scan A 72cf942ee2d9
loop is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 1,085 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-31.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.