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.
npx agentmods add commands/pydantic/skills/debuggit clone --depth 1 https://github.com/pydantic/skillsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00013 | $0.00529 |
| Opus 5 | $0.00006 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug
Use the Logfire MCP server to investigate errors and debug issues using real trace data.
If the user only asks to open, view in browser, use the live view, open Explore, or get a Logfire link, use logfire-ui instead of this query-first debugging workflow. For ambiguous prompts such as "show recent errors", ask whether they want UI or query analysis first.
Prerequisites
The Logfire MCP server must be connected (this plugin configures it automatically). The user must have run logfire auth or set LOGFIRE_TOKEN for their project.
Workflow
When the user reports an error in a specific file
- Call the
find_exceptions_in_fileMCP tool with the file path to get the 10 most recent exceptions from that file. - Show the user the exceptions found - include the exception type, message, and when it occurred.
- If a specific exception is relevant, use
arbitrary_queryto dig deeper into the surrounding trace context. - Suggest a fix based on the exception details and trace data.
When the user asks about general issues or wants debugging analysis
- Call
get_logfire_records_schemato understand the available columns and tables. - Use
arbitrary_queryto run SQL queries against the OpenTelemetry data. Common queries:- Recent errors:
SELECT start_timestamp, message, attributes FROM records WHERE level = 'error' ORDER BY start_timestamp DESC LIMIT 20 - Slow operations:
SELECT span_name, duration, start_timestamp FROM records WHERE duration > interval '1 second' ORDER BY duration DESC LIMIT 20 - Specific endpoint issues:
SELECT * FROM records WHERE attributes->>'http.route' = '/api/users' AND level = 'error' ORDER BY start_timestamp DESC LIMIT 10
- Recent errors:
- Present findings and suggest fixes.
When analysis identifies a trace the user wants to share
- Use the configured Logfire link tool, such as
project_logfire_link(trace_id=trace_id, project=project), to generate a shareable URL for that specific trace. - Share the link with the user.
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.
- 2d ago First seen · 46 lines · 13 tokens per session scan A ab07946c35ef
debug is a command published in the GitHub repository pydantic/skills (127 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 529 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.