cancel-loop

A command that stops an active Loopback loop, an automated cycle that repeats work until its saved state is removed.

In plain words
What is it for?
Use it to inspect the current iteration, remove the loop's state file, and report that the loop was cancelled.
Why use it?
It provides a way to end the cycle and prevents the wrapper from continuing at its next check.

Command

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 commands/okwinds/miscellany/cancel-loop
Clone the repo
git clone --depth 1 https://github.com/okwinds/miscellany
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 259 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.00005 $0.00259
Opus 5 $0.00003 $0.00130
Sonnet 5 $0.00001 $0.00052
Haiku 4.5 $0.00001 $0.00026

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

Security

Grade A, and why

cancel-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.

agent/skills/loopback/commands/cancel-loop.md · 22 lines

What it actually says

Cancel Loopback

To cancel the Loopback loop:

  1. Check if .codex/loopback.local.md exists using Bash: test -f .codex/loopback.local.md && echo "EXISTS" || echo "NOT_FOUND"

  2. If NOT_FOUND: Say "未找到活动的 Loopback 循环。"

  3. If EXISTS:

    • 读取 .codex/loopback.local.md 获取 iteration: 字段中的当前迭代次数
    • 使用 Bash 删除文件: rm .codex/loopback.local.md
    • 报告: "已取消 Loopback 循环 (当前迭代次数: N)",其中 N 是迭代值

Note:

  • 如果你正在运行 scripts/codex-loopback-wrapper.sh,删除状态文件会让 wrapper 在下一次检查时退出(视为取消)。
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 · 22 lines · 5 tokens per session scan A a2a7d31693b1

Subscribe to this mod's changes

cancel-loop is a command published in the GitHub repository okwinds/miscellany (50 stars, last pushed 3mo ago), licensed MIT. It adds 5 tokens to every session and 259 once invoked, about $0.0000 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.