loop

A recurring-task workflow for running a prompt or skill repeatedly at a fixed interval, such as every five minutes, or at changing intervals chosen after each run.

In plain words
What is it for?
Use it to run recurring prompts, monitor local shell output, check deployments, run tests, or generate periodic reports. It can run the prompt once immediately and then continue on schedule.
Why use it?
It removes the need to manually repeat checks or commands and keeps track of an already-running matching loop to avoid duplicates.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/taurus42119-stack/godkiller-mcp/loop
Any agent
npx skills add taurus42119-stack/godkiller-mcp --skill loop
Clone the repo
git clone --depth 1 https://github.com/taurus42119-stack/godkiller-mcp

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 913 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00028 $0.00913
Opus 5 $0.00014 $0.00456
Sonnet 5 $0.00006 $0.00183
Haiku 4.5 $0.00003 $0.00091

Measured 2d ago against content hash 03f141406a7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • loop — 100% identical, 0 lines differ
src/godkiller_mcp/bundled_skills/agent-ops/loop/SKILL.md · 74 lines

How it starts

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

Loop

Parse

Accept /loop [interval] <prompt>.

  • Leading interval: 5m /foo, 30s check status, 2h run report.
  • Trailing interval: check deploy every 5m, run tests every 10 minutes.
  • No interval: dynamic mode; the agent chooses the next delay after each run.
  • Empty prompt: show Usage: /loop [interval] <prompt>.

Use intervals like 30s, 5m, 2h, 1d. Convert unit words to short units.

Use monitored shell output to wake the agent for recurring local work.

Fixed Schedule

while true; do
  sleep <seconds>
  echo 'AGENT_LOOP_TICK_<purpose> {"prompt":"<prompt>"}'
done
  1. Check existing terminals for an already-running matching loop.
  2. Start one background shell loop with notify_on_output.
  3. Use a unique sentinel and a regex such as ^AGENT_LOOP_TICK_<purpose>.
  4. Smoke-check once to confirm clean startup.
  5. Run the prompt once immediately after arming the loop.
  6. The first sentinel should arrive only after the initial sleep, so startup does not double-run the prompt.
  7. Track the PID so the agent can stop the loop if asked.
  8. Briefly confirm: the interval, that the prompt already ran once, when the first tick will arrive, and that the loop will fire on each tick until stopped. On later ticks, give a short update of what changed. On stop, say the loop has stopped and why.

Dynamic Schedule

The user wants the agent to self-pace. Decide what makes the next iteration worth running — a passage of time, or an observable event.

  1. Run the prompt now.
  2. If the next run is gated on an event (a git ref advancing, a log line matching, a file changing, a CI check completing), arm a background watcher that emits the sentinel only when the event fires, with notify_on_output on ^AGENT_LOOP_WAKE_<purpose>. Arm once; skip on later ticks if it's still running.
  3. At the end of the turn, arm a one-shot time-based wake:
sleep <seconds>
echo 'AGENT_LOOP_WAKE_<purpose> {"prompt":"<prompt>"}'

With a watcher armed, this is the fallback heartbeat — lean long so idle ticks aren't pure overhead. Without a watcher, this is the cadence — pick a delay based on when the result is worth checking again.

Read the full file on GitHub · 74 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. 2d ago First seen · 74 lines · 28 tokens per session scan A 03f141406a7e

Subscribe to this mod's changes

loop is a skill published in the GitHub repository taurus42119-stack/godkiller-mcp (22 stars, last pushed 24d ago), licensed MIT. It adds 28 tokens to every session and 913 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-30.

Related

Other skills, from other repositories

ag-sdd

Activates the Anti-Gravity Spec-Driven Development (ag-sdd) workflow. Use this skill when the user asks to implement a feature, fix a bug, or write code in a repository that uses ag-sdd. It enforces a strict 4-phase SDD lifecycle: Discovery, Spec Generation, Sequential Execution, and Quality Signoff.

stormlive-ai/ag-sdd · 78 tokens

agent-self-scheduling

Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.

sickn33/agentic-awesome-skills · 24 tokens

cao-workflow

Author and run CAO Python workflow scripts — multi-step, parameterized, fan-out orchestrations executed by cao workflow run. Use when the user wants a repeatable multi-step job (e.g. data analysis over many files, a review pipeline, a parameterized batch). Authoring ends at a validated script file; running it is a…

awslabs/cli-agent-orchestrator · 79 tokens

aidlc-portfolio

Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…

awslabs/cli-agent-orchestrator · 74 tokens

cao-plugin

Create a new CAO (CLI Agent Orchestrator) plugin. Use this skill whenever the user wants to add a plugin that reacts to CAO lifecycle or messaging events, scaffold a plugin package, understand plugin requirements, or integrate an external system (Discord, Slack, dashboards, logging, metrics) with CAO. Also use when…

awslabs/cli-agent-orchestrator · 96 tokens

cao-provider

Create a new CLI agent provider for CAO (CLI Agent Orchestrator). Use this skill whenever the user wants to add support for a new CLI-based AI agent (e.g., a new coding assistant CLI), integrate a new provider, or scaffold a provider implementation. Also use when the user asks about the provider architecture, what…

awslabs/cli-agent-orchestrator · 81 tokens