break-loop

break-loop is a skill for Claude Code, Codex from lxyer/multi-agent-collaboration-system. It costs 81 tokens per session (1,115 once invoked), scanned A, original, MIT.

A post-debugging review guide for finding why a bug happened and why earlier fixes may have failed. It also records lessons in project documentation.

In plain words
What is it for?
It is for reviewing root causes, incomplete or misleading fixes, missing tests, unclear interfaces between code layers, and undocumented assumptions after a difficult bug.
Why use it?
It helps teams avoid fixing the same class of bug repeatedly by turning a completed debugging session into specific prevention steps.

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/lxyer/multi-agent-collaboration-system/break-loop
Any agent
npx skills add lxyer/multi-agent-collaboration-system --skill break-loop
Clone the repo
git clone --depth 1 https://github.com/lxyer/multi-agent-collaboration-system

Made for: Claude Code, Codex.

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 break-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/lxyer/multi-agent-collaboration-system/break-loop.svg)](https://agentmods.dev/skills/lxyer/multi-agent-collaboration-system/break-loop)
Your own site
<a href="https://agentmods.dev/skills/lxyer/multi-agent-collaboration-system/break-loop"><img src="https://agentmods.dev/badge/skills/lxyer/multi-agent-collaboration-system/break-loop.svg" alt="Measured on agentmods" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,115 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.00081 $0.01115
Opus 5 $0.00041 $0.00558
Sonnet 5 $0.00016 $0.00223
Haiku 4.5 $0.00008 $0.00112

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

Security

Grade A, and why

break-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 4d 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.

.agents/skills/break-loop/SKILL.md · 131 lines

How it starts

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

Break the Loop - Deep Bug Analysis

When debug is complete, use this skill for deep analysis to break the "fix bug -> forget -> repeat" cycle.


Analysis Framework

Analyze the bug you just fixed from these 5 dimensions:

1. Root Cause Category

Which category does this bug belong to?

Category Characteristics Example
A. Missing Spec No documentation on how to do it New feature without checklist
B. Cross-Layer Contract Interface between layers unclear API returns different format than expected
C. Change Propagation Failure Changed one place, missed others Changed function signature, missed call sites
D. Test Coverage Gap Unit test passes, integration fails Works alone, breaks when combined
E. Implicit Assumption Code relies on undocumented assumption Timestamp seconds vs milliseconds

2. Why Fixes Failed (if applicable)

If you tried multiple fixes before succeeding, analyze each failure:

  • Surface Fix: Fixed symptom, not root cause
  • Incomplete Scope: Found root cause, didn't cover all cases
  • Tool Limitation: grep missed it, type check wasn't strict
  • Mental Model: Kept looking in same layer, didn't think cross-layer

3. Prevention Mechanisms

What mechanisms would prevent this from happening again?

Type Description Example
Documentation Write it down so people know Update thinking guide
Architecture Make the error impossible structurally Type-safe wrappers
Compile-time TypeScript strict, no any Signature change causes compile error
Runtime Monitoring, alerts, scans Detect orphan entities
Test Coverage E2E tests, integration tests Verify full flow
Code Review Checklist, PR template "Did you check X?"

4. Systematic Expansion

What broader problems does this bug reveal?

  • Similar Issues: Where else might this problem exist?
  • Design Flaw: Is there a fundamental architecture issue?
  • Process Flaw: Is there a development process improvement?
  • Knowledge Gap: Is the team missing some understanding?

Read the full file on GitHub · 131 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. 4d ago First seen · 131 lines · 81 tokens per session scan A c947b0fc673b

Subscribe to this mod's changes

break-loop is a skill published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 4mo ago), licensed MIT. It adds 81 tokens to every session and 1,115 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

workflow-guide

创建、编辑、校验、运行或排查 DeterminFlow 工作流时必须先加载此技能;也适用于任务填参、节点审批、变量传递、网关、执行方案、子流程与工作区覆盖。涉及 Agent 定义、Prompt 模板或 Script Library 的专项设计时,继续加载对应 Core Skill。.

alikon-art/DeterminFlow · 75 tokens

agent-definition-guide

创建、修改、删除或排查 DeterminFlow Agent Definition 时必须加载此技能;也适用于选择 agenttype、最小工具权限、Prompt 模板绑定、模型覆盖、Skill/Rule 可见分组、子会话可用性与 Workflow Agent 节点配置。.

alikon-art/DeterminFlow · 65 tokens

prompt-template-guide

查看、创建、修改、删除或排查 DeterminFlow Prompt Template 与 system prompt section 时必须加载此技能;也适用于 section 顺序、workflowonly/chatonly、cache break、自定义 templatevariables、系统变量渲染以及 Agent Definition 的 prompttemplate 绑定。.

alikon-art/DeterminFlow · 62 tokens

script-library-guide

创建、更新、删除、引用或排查 DeterminFlow Script Library 脚本时必须加载此技能;也适用于 Workflow Script 节点、inline 与 library 选择、SCRIPT.md、scriptargv、共享 workspace、WFVAR/scriptout 输出协议、Plugin 脚本 owner 冲突与 Task 身份冻结。.

alikon-art/DeterminFlow · 76 tokens

skill-rule-authoring-guide

创建、更新、修补、删除、分组或排查 DeterminFlow Skill 与 Rule 时必须加载此技能;也适用于判断知识应进入 Skill、强制约束应进入 Rule、运行时 data/skills 与版本化 Core Skills 的边界、Plugin 只读资源以及幽灵配置清理。.

alikon-art/DeterminFlow · 75 tokens

automation-guide

创建、查看、更新、暂停、恢复、立即运行、删除或排查 DeterminFlow Cron 自动化任务时必须加载此技能;也适用于 once/interval/cron 调度、时区、Agent 类型与权限、重复次数、静默输出、失败重试和历史输出核验。.

alikon-art/DeterminFlow · 68 tokens