debugger

A debugging assistant for finding the causes of errors, failed tests, and unexpected program behavior.

In plain words
What is it for?
Use it to investigate error messages, test failures, and software that does not behave as expected.
Why use it?
It helps narrow down problems when the cause is unclear, including issues that appear during development or testing.

Agent

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 agents/composio-community/awesome-claude-plugins/debugger
Clone the repo
git clone --depth 1 https://github.com/composio-community/awesome-claude-plugins
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 165 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00023 $0.00165
Opus 5 $0.00012 $0.00082
Sonnet 5 $0.00005 $0.00033
Haiku 4.5 $0.00002 $0.00016

Measured 2d ago against content hash 4332c8994244, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debugger 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.

debugger/agents/debugger.md · 30 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 30 lines · 23 tokens per session scan A 4332c8994244

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository composio-community/awesome-claude-plugins (1,916 stars, last pushed 1mo ago), with no licence file. It adds 23 tokens to every session and 165 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.

Related

Other agents, from other repositories

checklist-manager

Scan and analyze checklists in the project, return summary for user decision.

Marcel-Bich/marcel-bich-claude-marketplace · 18 tokens

code-commit

Git commit specialist with deep knowledge of version control best practices and semantic commit messages. Automatically runs language-specific quality checks (formatters and type checkers) before committing code changes. Use when ready to commit changes to git.

RoniLeor/specWeaver · 47 tokens

code-consolidator

Documentation architect specializing in creating precise, consolidated technical documentation. Analyzes existing documentation patterns, eliminates duplication, and maintains consistency across large codebases. Use proactively when features are completed or documentation needs review.

RoniLeor/specWeaver · 44 tokens

code-reviewer

Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.

RoniLeor/specWeaver · 39 tokens

code-architect

Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences.

RoniLeor/specWeaver · 40 tokens

code-explorer

Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.

RoniLeor/specWeaver · 33 tokens