debug

debug is a command for Claude Code from pydantic/skills. It costs 13 tokens per session (75 once invoked), scanned A, original, MIT.

A debugging command that uses Logfire trace data to investigate application errors. A trace is a recorded path showing what happened during an operation, often across several components.

In plain words
What is it for?
Use it to find recent exceptions in a file, inspect related trace records, query Logfire data, and suggest fixes based on the observed failure.
Why use it?
It helps identify the cause and surrounding context of production failures instead of relying only on an error message or source code.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the logfire plugin — 10 skills, 7 commands, 1 MCP server shipped together

Good fit Use it to find recent exceptions in a file, inspect related trace records, query Logfire data, and suggest fixes based on the observed failure.

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

Clone the repo
git clone --depth 1 https://github.com/pydantic/skills

Made for: Claude Code.

Or install logfire, the plugin that ships this one along with the rest of its 10 skills, 7 commands, 1 MCP server.

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/commands/pydantic/skills/debug/github.svg)](https://agentmods.dev/commands/pydantic/skills/debug)
Your own site
<a href="https://agentmods.dev/commands/pydantic/skills/debug"><img src="https://agentmods.dev/badge/commands/pydantic/skills/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/commands/pydantic/skills/debug"><img src="https://agentmods.dev/badge/commands/pydantic/skills/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 75 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.00013 $0.00075
Opus 5.5 $0.00005 $0.00030
Sonnet 5.5 $0.00003 $0.00015
Haiku 4.5 $0.00001 $0.00007

Measured 26d ago against content hash 7590d0ba60b3, 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 26d 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.

plugins/logfire/commands/debug.md · 12 lines

What it actually says

/debug

Load and follow the logfire-query skill for evidence-backed investigation. If the user wants a browser view or link rather than analysis in chat, use the logfire-ui skill instead. The user's instructions take precedence over both skills.

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. 26d ago Changed · -34 lines 7590d0ba60b3
  2. 2mo ago First seen · 46 lines · 13 tokens per session scan A ab07946c35ef

Subscribe to this mod's changes

debug is a command published in the GitHub repository pydantic/skills (151 stars, last pushed 9d ago), licensed MIT. It adds 13 tokens to every session and 75 once invoked, about $0.0001 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 compared with commands from other repositories

debug next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
debugpydantic/skillsCommand1519d agoMITA13Claude Code
qa-changesOpenHands/extensionsCommand176yesterdayMITA63Claude Code
react-nativegetsentry/toolkitCommand957yesterdaynoneA0Claude Code
auditar-cascadingluanpdd/kit-mcpCommand54d agoMITA54Claude Code
http-serviceMadAppGang/magusCommand14yesterdayMITA27Claude Code
doctordoncheli/don-cheli-sddCommand592mo agoApache-2.0A76Claude Code
doctorfatihkan/badiCommand71mo agoMITA0Claude Code