debug-loop

A debugging workflow for creating a reliable failing feedback loop before investigating difficult bugs, flaky tests, regressions, or performance problems.

In plain words
What is it for?
It is for debugging hard-to-reproduce failures, unstable tests, newly introduced bugs, and slow-running code.
Why use it?
It helps establish a repeatable way to observe the problem before attempting a diagnosis.

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/me-cedric/agent-compass/debug-loop
Any agent
npx skills add me-cedric/agent-compass --skill debug-loop
Clone the repo
git clone --depth 1 https://github.com/me-cedric/agent-compass

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 320 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00024 $0.00320
Opus 5 $0.00012 $0.00160
Sonnet 5 $0.00005 $0.00064
Haiku 4.5 $0.00002 $0.00032

Measured yesterday against content hash 915a43f7974d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debug-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 yesterday.

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.

skills/debug-loop/SKILL.md · 51 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 51 lines · 24 tokens per session scan A 915a43f7974d

Subscribe to this mod's changes

debug-loop is a skill published in the GitHub repository me-cedric/agent-compass (2 stars, last pushed 4d ago), with no licence file. It adds 24 tokens to every session and 320 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-31.