agentmods.dev

vibe-debug CLAUDE.md

A debugging instruction set for Python problems that can be reproduced with a script, test, command, or request.

In plain words
What is it for?
It helps investigate branch-dependent failures, inspect runtime state at a chosen line, evaluate read-only expressions, and report observed values separately from assumptions.
Why use it?
It reduces guesswork by encouraging developers to inspect the program while it is running, including its current values and local variables.

Instructions file

27 3mo ago A scan 215 tokens copy · 100% MIT
View the source file illscience/vibe-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.

agentmods
npx agentmods add instructions/illscience/vibe-debug/claude-md
Clone the repo
git clone --depth 1 https://github.com/illscience/vibe-debug
Per session 215 This file is loaded in full into every session.
When invoked 215 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00215 $0.00215
Opus 5 $0.00108 $0.00108
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00021 $0.00021

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

Security

Grade A, and why

vibe-debug CLAUDE.md 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.

Origin

This is a copy

100% identical to vibe-debug AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 18 lines

What it actually says

Debugging Workflow

When a Python bug has a reproducible script, test, command, or request, prefer observing live runtime state before proposing a fix.

Use the vibe-debug skill or CLI when:

  • the failure depends on branches, inputs, object state, or local variables;
  • source reading suggests multiple possible causes;
  • you are about to infer a variable value that can be observed directly.

Recommended workflow:

  1. Use the vibe-debug skill if it is available in this project.
  2. Run npx -y github:illscience/vibe-debug debug-python <script.py> --break <file.py>:<line> --json.
  3. Inspect the stopped location, locals, and evaluations.
  4. Use --eval only for read-style expressions; it can execute code in the debuggee.
  5. If an MCP server named vibe-debug is installed, debug_python_repro is also acceptable.

When reporting a bug, include the runtime values you observed and distinguish them from source-code inference.

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 · 18 lines · 215 tokens per session scan A cfc2691b9f9e

Subscribe to this mod's changes

vibe-debug CLAUDE.md is an instructions file published in the GitHub repository illscience/vibe-debug (27 stars, last pushed 3mo ago), licensed MIT. It adds 215 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-debug AGENTS.md, differing in 0 lines, and is treated as a copy.

DebuggingGit and workflowTestingclaude-codecodexcoding-agentsdapdebuggerdebugpy
Related

Other instructions, from other repositories

debugium CLAUDE.md

Claude Code instructions for Algiras/debugium, covering debugium — claude code instructions, setup, 1. install debugium, 2. register the mcp server and 3. launch a debug session.

Algiras/debugium · 2,471 tokens

ontology-atlas AGENTS.md

Instructions for wlsdks/ontology-atlas, covering agents.md — ontology-atlas, product and non-negotiable architecture, start here, structure and routes and operating gates and skills.

wlsdks/ontology-atlas · 2,685 tokens

ephemeral-sandbox CLAUDE.md

Instructions for Ephemeral-AI-Lab/ephemeral-sandbox, covering claude.md, project, engineering practice (required), build & test and sandbox tools.

Ephemeral-AI-Lab/ephemeral-sandbox · 1,203 tokens

matt-skills-with-to-goal CLAUDE.md

Instructions for tt-a1i/matt-skills-with-to-goal: Skills are organized into bucket folders under skills/.

tt-a1i/matt-skills-with-to-goal · 989 tokens

coral CLAUDE.md

Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).

cdknorow/coral · 1,898 tokens

pixir CLAUDE.md

Instructions for Ranvier-Technologies/pixir, covering pixir harness - legacy agent guide, current map and commands.

Ranvier-Technologies/pixir · 246 tokens