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 skills/restarter/lets-workflow/loop-testnpx skills add restarter/lets-workflow --skill loop-testgit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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.00112 | $0.02303 |
| Opus 5 | $0.00056 | $0.01151 |
| Sonnet 5 | $0.00022 | $0.00461 |
| Haiku 4.5 | $0.00011 | $0.00230 |
Grade A, and why
loop-test 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 yesterday.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop-test (local experiment)
/loop schedules periodic re-invocations of the same prompt. Two modes:
| Mode | Syntax | Mechanic |
|---|---|---|
| Interval | /loop 5m /foo · /loop /standup 1h · /loop check the deploy every 20m |
Cron entry in .claude/scheduled_tasks.json. Default 10m when only [interval] shorthand. Survives session restart (durable). |
| Dynamic / self-paced | /loop check the deploy (no interval anywhere) |
Model calls ScheduleWakeup(delaySeconds, prompt, reason) at the end of each turn. Skip → loop ends silently. |
/loop is the wrong tool for sequential workflow phases. It repeats the same prompt each tick — to chain plan → review → check, the prompt itself has to be phase-aware (read state, advance, write back). For state-convergent autonomy, use /goal instead (see goal-test skill).
Right tool for /loop:
- Polling external state (CI runs, deploys, PR comments)
- Periodic checks (every 20m: any new bd-ready tasks?)
- Babysitting a long-running job (check progress, surface failures)
- Continuous monitoring during a long focused session
How /loop actually works
Reverse-engineered from claude binary v2.1.150.
Dynamic-mode contract
This is the mode you care about most — interval is just cron.
- User runs
/loop <prompt>(no interval). - Model does the work.
- Before yielding, model calls
ScheduleWakeup(delaySeconds, prompt, reason):delaySecondsclamped to[60, 3600]promptmust be exactly the same string as the original/loopinputreasonis one sentence shown to user + sent to telemetry — be specific ("polling CI run"beats"waiting")
- Harness re-invokes the model at the scheduled time. Loop continues.
- Skip
ScheduleWakeup→ loop ends silently. No error.
Cache TTL gotcha
Anthropic prompt cache TTL is 5 minutes. Picking delaySeconds:
< 270s→ cache stays warm, cheap re-invocation>= 1200s→ commit to the miss, one cache-miss amortizes over a long wait300sis worst-of-both — you pay the miss without amortizing. Avoid exactly 300.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 173 lines · 112 tokens per session scan A 0525b5d511aa
loop-test is a skill published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 112 tokens to every session and 2,303 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…