loop

loop is a skill for Claude Code from asgeirtj/system_prompts_leaks. It costs 36 tokens per session (1,777 once invoked), scanned A, original, CC0-1.0.

A command for running a prompt or slash command repeatedly at a chosen interval.

In plain words
What is it for?
It is for recurring checks, monitoring logs or CI, and repeating agent tasks on a fixed or automatically chosen schedule.
Why use it?
It avoids restarting the same check by hand and can adjust the timing when the work depends on an event such as a build finishing.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Good fit It is for recurring checks, monitoring logs or CI, and repeating agent tasks on a fixed or automatically chosen schedule.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asgeirtj/system_prompts_leaks/loop
About the project

System Prompts Leaks is a collection of captured system instructions used to guide AI chatbots and coding agents before they receive user messages. It serves researchers and developers studying how different AI assistants are directed.

asgeirtj/system_prompts_leaks · 64,387 stars · on GitHub

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.

Any agent
npx skills add asgeirtj/system_prompts_leaks --skill loop
Clone the repo
git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/asgeirtj/system_prompts_leaks/loop.svg)](https://agentmods.dev/skills/asgeirtj/system_prompts_leaks/loop)
Your own site
<a href="https://agentmods.dev/skills/asgeirtj/system_prompts_leaks/loop"><img src="https://agentmods.dev/badge/skills/asgeirtj/system_prompts_leaks/loop.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,777 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. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review Third-party audits
  • Snyk warn 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00036 $0.01777
Opus 5 $0.00018 $0.00889
Sonnet 5 $0.00007 $0.00355
Haiku 4.5 $0.00004 $0.00178

Measured 8d ago against content hash a278f6ea693b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

Anthropic/claude-code/skills/loop/SKILL.md · 51 lines

How it starts

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

/loop — autonomous default with dynamic pacing

The user invoked /loop with no prompt and no interval. Run the autonomous check now, then self-pace the next iteration via ScheduleWakeup — no cron.

Action

  1. Run the autonomous check now, following the instructions inlined below.
  2. If the next tick is gated on an event (CI finishing, a PR comment, a log line) and no Monitor is already running for it: arm one now with persistent: true. Its events wake this loop immediately — you do not wait for the ScheduleWakeup deadline. Arm once; on later ticks call TaskList first and skip if a monitor is already running.
  3. Briefly confirm: that this is the autonomous default in dynamic-pacing mode, that you ran the check now, whether a Monitor is the primary wake signal, and what fallback delay you're about to pick. Write this as text before calling ScheduleWakeup — the turn ends as soon as that tool returns.
  4. Then, as the last action of this turn, decide whether the loop continues. If the next check is worth running, call ScheduleWakeup with:
    • delaySeconds: with a Monitor armed this is the fallback heartbeat (lean 1200–1800s). Without one, pick based on what you observed this turn — quiet branch? wait longer. Lots in flight? wait shorter. Read the tool's own description for cache-aware delay guidance.
    • reason: one short sentence on why you picked that delay.
    • prompt: the literal string <<autonomous-loop-dynamic>> — the dynamic-mode sentinel expands at fire time to the full instructions (first fire / first fire post-compact / loop.md edited) or a dynamic-pacing-specific short reminder (subsequent fires). Do not pass the full instructions; that is handled automatically.
    • noop: true if this tick changed nothing ("still waiting", "quiet hold"); false if it did something worth keeping. Consecutive noop: true ticks collapse in the terminal. If it isn't, stop instead (step 6) — re-arming is a per-turn choice, not a default.
  5. If woken by a <task-notification> rather than this prompt: handle the event, then make the same decision. If the loop should continue, call ScheduleWakeup again with <<autonomous-loop-dynamic>> and the same 1200–1800s delaySeconds (the Monitor remains the wake signal; the new wakeup is only the fallback heartbeat). If the event means the work is finished, stop (step 6).
  6. To stop the loop — the task is complete, further iterations can't make progress, or the user asked you to stop — call ScheduleWakeup with stop: true (no other fields) and TaskStop any Monitor you armed (use TaskList to find the task ID if it is no longer in context). Stopping is the loop's normal ending — the user can restart it anytime with /loop. Before you stop, send a one-line outcome via PushNotification — the user may be away and waiting to hear it's done. Skip this if you're stopping because the user just told you to; they're already here.

Read the full file on GitHub · 51 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. 8d ago First seen · 51 lines · 36 tokens per session scan A a278f6ea693b

Subscribe to this mod's changes

loop is a skill published in the GitHub repository asgeirtj/system_prompts_leaks (64,387 stars, last pushed today), licensed CC0-1.0. It adds 36 tokens to every session and 1,777 once invoked, about $0.0002 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.