debug

debug is a skill for Claude Code, Codex from samibs/skillfoundry. It costs 7 tokens per session (591 once invoked), scanned A, original, MIT.

An interactive debugger for pausing a program, setting breakpoints, stepping through code, and inspecting what the program is doing.

In plain words
What is it for?
Use it to debug source files, pause at a chosen line, or step through tests run with tools such as Jest, Vitest, Pytest, or Mocha.
Why use it?
It helps locate the cause of a bug by showing the program's state at specific points instead of relying only on logs or guesses.

Skill for Claude CodeCodex

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

Good fit Use it to debug source files, pause at a chosen line, or step through tests run with tools such as Jest, Vitest, Pytest, or Mocha.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/samibs/skillfoundry/debug
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.

Any agent
npx skills add samibs/skillfoundry --skill debug
Clone the repo
git clone --depth 1 https://github.com/samibs/skillfoundry

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/samibs/skillfoundry/debug/github.svg)](https://agentmods.dev/skills/samibs/skillfoundry/debug)
Your own site
<a href="https://agentmods.dev/skills/samibs/skillfoundry/debug"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/debug/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

Your own site · 80×15
<a href="https://agentmods.dev/skills/samibs/skillfoundry/debug"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 591 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.
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.00007 $0.00591
Opus 5.5 $0.00003 $0.00236
Sonnet 5.5 $0.00001 $0.00118
Haiku 4.5 $0.00001 $0.00059

Measured 1mo ago against content hash 9b421b0166a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

debug 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 1mo 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/SKILL.md · 82 lines

How it starts

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

Debug — Interactive Debugger

Role: Launch and control an interactive debug session for a file, test, or running process.


Usage

/debug <file>              Start debug session, paused at entry
/debug <file>:<line>       Start session with breakpoint at line
/debug test <test-file>    Debug a test file using its test runner

Examples

/debug src/auth/login.ts
/debug src/utils/parser.ts:42
/debug test src/auth/__tests__/login.test.ts

Behavior

When invoked, follow this sequence:

1. Start Session

  • Parse the argument to extract file path and optional line number.
  • If prefixed with test, detect the test runner (jest, vitest, pytest, mocha) from project config.
  • Call debug_start with the resolved file, runtime, and test_command if applicable.
  • Confirm the session started and report the paused location.

2. Set Initial Breakpoint (if line specified)

  • If the user provided <file>:<line>, call debug_breakpoint with action set at that line.
  • Then call debug_step with action continue to run to the breakpoint.
  • Report the paused location and surrounding code context.

3. Guide Inspection

  • Once paused, call debug_inspect with target scope to show local variables.
  • Call debug_inspect with target callstack to show the call stack.
  • Present findings and ask the user what to investigate next.

4. Interactive Loop

Respond to user instructions by mapping them to debug tools:

User says Tool call
"step" / "next" debug_step action=next
"step into" debug_step action=into
"step out" debug_step action=out
"continue" debug_step action=continue
"inspect X" debug_inspect target=X
"eval " debug_evaluate expression=expr
"break :" debug_breakpoint action=set
"breakpoints" debug_breakpoint action=list
"stop" / "quit" debug_stop

5. Cleanup

  • Always call debug_stop when the user is done or the process exits.
  • Report any uncaught exceptions with full stack trace and variable context.

Read the full file on GitHub · 82 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. 1mo ago First seen · 82 lines · 7 tokens per session scan A 9b421b0166a2

Subscribe to this mod's changes

debug is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 14d ago), licensed MIT. It adds 7 tokens to every session and 591 once invoked, about $0.0000 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

Other skills, from other repositories

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

issue-root-resolution

Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.

Gentleman-Programming/gentle-ai · 45 tokens

rdd-defect-workflow

Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.

Gentleman-Programming/gentle-ai · 41 tokens

roam

Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…

Cranot/roam-code · 86 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

memorix-troubleshooting

Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.

AVIDS2/memorix · 36 tokens