agentmods.dev

loop

A recurring-task tool for Codex that runs a prompt again at a chosen interval. It can also show, pause, resume, cancel, and finish those tasks.

In plain words
What is it for?
Repeated jobs such as checking a deployment every few minutes. It also helps manage the scheduled runs afterward.
Why use it?
It removes the need to remember and manually repeat checks or other prompts. It can keep task runs tied to a visible Codex session.

Skill for Claude CodeCodex

9 4mo ago A scan 54 tokens original MIT
View the source file Owen718/codex-loop-plugin
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/owen718/codex-loop-plugin/loop
Any agent
npx skills add Owen718/codex-loop-plugin --skill loop
Clone the repo
git clone --depth 1 https://github.com/Owen718/codex-loop-plugin

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 863 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.00054 $0.00863
Opus 5 $0.00027 $0.00432
Sonnet 5 $0.00011 $0.00173
Haiku 4.5 $0.00005 $0.00086

Measured 2d ago against content hash 76952dec195c, 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.

plugins/codex-loop/skills/loop/SKILL.md · 61 lines

How it starts

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

Codex Loop

This skill is the user-facing entrypoint for the Codex Loop plugin. It parses the user intent, calls the codex_loop MCP tools, and relies on codex-loopd or the optional Stop hook fallback to trigger future iterations. New tasks default to visibility_policy=visible_only and runner=app-server: if the task cannot bind to a concrete current Codex session/thread id, or no app-server runtime is configured, it pauses instead of starting a hidden new session. The MCP tool starts codex-loopd automatically when the selected runner is runnable unless CODEX_LOOP_AUTOSTART=0.

Supported user forms

  • $loop 5m check deploy
  • $loop check deploy
  • $loop 15m
  • $loop
  • $loop list
  • $loop cancel <job_id>
  • $loop pause <job_id>
  • $loop resume <job_id>
  • /prompts:loop 5m check deploy

For Claude Code style visible loop turns, launch Codex through the repository script first:

  • codex-loop tui --cwd <repo>

This starts a local app-server runtime, starts codex-loopd against it, writes the active runtime marker, and opens codex --remote with the CODEX_LOOP_APP_SERVER, token file, and runtime DB environment needed by visible_only loop tasks.

Behavior

  1. If the request is create-like, call mcp__codex_loop__loop_create with:
    • raw_user_input: the raw arguments after $loop or /prompts:loop
    • cwd: current working directory
    • thread_id: the current Codex thread id. Prefer the CODEX_THREAD_ID environment variable. If it is not already visible, run printf '%s\n' "$CODEX_THREAD_ID" and pass the non-empty value.
    • approval_policy, sandbox, model: current snapshots if known; omit unknown values
  2. If the user asks for list/status, call mcp__codex_loop__loop_list.
  3. If the user asks to cancel/delete/rm, call mcp__codex_loop__loop_delete with job_id.
  4. If the user asks pause/resume, call mcp__codex_loop__loop_update.
  5. After a scheduled iteration prompt explicitly asks you to complete the iteration, call mcp__codex_loop__loop_complete_iteration.
    • Include both job_id and run_id when the prompt provides them. Completion is idempotent per run_id.

Read the full file on GitHub · 61 lines

Files

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.

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 · 61 lines · 54 tokens per session scan A 76952dec195c

Subscribe to this mod's changes

loop is a skill published in the GitHub repository Owen718/codex-loop-plugin (9 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 863 once invoked, about $0.0003 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.

Data and AIDevOps and cloudPlanning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens