Forge-Agentic-Coding-CLI: Skill for Claude Code

.agents/skills/debug-loop/SKILL.md

debug-loop is a skill for Claude Code, Codex from hoangsonww/Forge-Agentic-Coding-CLI. It costs 43 tokens per session (398 once invoked), scanned A, original, MIT.

A systematic debugging playbook for Forge's agent loop, the part that coordinates model turns and tool calls. It uses logs, event streams, focused checks, and a failing test before the fix.

In plain words
What is it for?
Reproducing loop problems, inspecting session events, checking turn caps and validation, finding missing tools or denied permissions, and testing the eventual fix.
Why use it?
It gives developers a repeatable way to find whether looping or incorrect tool calls come from limits, validation, registration, permissions, or task state.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is hoangsonww/Forge-Agentic-Coding-CLI's own configuration. It tells Claude Code and Codex how to work on Forge-Agentic-Coding-CLI itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Forge-Agentic-Coding-CLI configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is FORGE_LOG_LEVEL=debug ./bin/forge.js <command>.

Reuse

Borrowing it

Nothing to install: this file belongs to hoangsonww/Forge-Agentic-Coding-CLI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hoangsonww/Forge-Agentic-Coding-CLI/master/.agents/skills/debug-loop/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLI

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/hoangsonww/forge-agentic-coding-cli/debug-loop/github.svg)](https://agentmods.dev/skills/hoangsonww/forge-agentic-coding-cli/debug-loop)
Your own site
<a href="https://agentmods.dev/skills/hoangsonww/forge-agentic-coding-cli/debug-loop"><img src="https://agentmods.dev/badge/skills/hoangsonww/forge-agentic-coding-cli/debug-loop/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for debug-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/hoangsonww/forge-agentic-coding-cli/debug-loop"><img src="https://agentmods.dev/badge/skills/hoangsonww/forge-agentic-coding-cli/debug-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 398 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00043 $0.00398
Opus 5.5 $0.00017 $0.00159
Sonnet 5.5 $0.00009 $0.00080
Haiku 4.5 $0.00004 $0.00040

Measured 2mo ago against content hash 03f16705b6ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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/debug-loop/SKILL.md · 50 lines

What it actually says

The loop is the most expensive place to be wrong. Instrument before you change anything.

1. Reproduce deterministically

FORGE_LOG_LEVEL=debug ./bin/forge.js <command>

Capture the session id. Events land in ~/.config/forge/events/<session>.ndjson.

If the bug only reproduces against a real provider, pin the model and disable router fallback:

FORGE_MODEL=... FORGE_ROUTER_FALLBACK=0 ./bin/forge.js <command>

2. Read the event stream, not the terminal

Each turn emits: turn.start, model.call, tool.call, tool.result, validation.result, turn.end. Missing or out-of-order events are your bug.

3. Check the usual suspects, in order

  1. Mode caps (src/core/mode-policy.ts) — is the agent hitting turn/token cap?
  2. Validation gate (src/core/validation.ts) — is a valid step being rejected?
  3. Tool registry — is the requested tool actually registered? tool.call with class: not_found means no.
  4. Permissions — silently denied? tool.result.denied=true.
  5. State machine (src/persistence/tasks.ts) — illegal transition attempted?

4. Add a failing test before the fix

Template: test/unit/executor-loop.test.ts. Mock callModel. If the test you add doesn't turn green after your fix, you fixed the wrong thing.

5. Finish with verify.

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. 2mo ago First seen · 50 lines · 43 tokens per session scan A 03f16705b6ff

Subscribe to this mod's changes

debug-loop is a skill published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (26 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 398 once invoked, about $0.0002 per session on Opus 5.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

debug-loop compared with skills from other repositories

debug-loop next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
debug-loophoangsonww/Forge-Agentic-Coding-CLISkill261mo agoMITA43Claude Code, Codex
hns-lsel-curatormodu-ai/moai-adkSkill1.3k4d agoApache-2.0A135Claude Code
moai-workflow-dddmodu-ai/moai-adkSkill1.3k4d agoApache-2.0A44Claude Code
moai-lane-watchdogmodu-ai/moai-adkSkill1.3k4d agoApache-2.0A86Claude Code
moai-workflow-loopmodu-ai/moai-adkSkill1.3k4d agoApache-2.0A44Claude Code
moai-workflow-testingmodu-ai/moai-adkSkill1.3k4d agoApache-2.0A47Claude Code
moai-fixmodu-ai/moai-adkSkill1.3k4d agoApache-2.0A21Claude Code