agent-debugger

An assistant for finding and explaining failures in ABCA agent runs, including setup checks, task execution, Python code, and CloudWatch logs.

In plain words
What is it for?
Use it to investigate failed tasks, preflight errors, agent execution problems, CloudWatch log output, and related Python agent code.
Why use it?
It helps identify why an agent task failed instead of requiring you to trace runtime messages and logs alone.

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/aws-samples/sample-autonomous-cloud-coding-agents/agent-debugger
Clone the repo
git clone --depth 1 https://github.com/aws-samples/sample-autonomous-cloud-coding-agents
Per session 237 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 801 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.00237 $0.00801
Opus 5 $0.00118 $0.00400
Sonnet 5 $0.00047 $0.00160
Haiku 4.5 $0.00024 $0.00080

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

Security

Grade A, and why

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

docs/abca-plugin/agents/agent-debugger.md · 81 lines

The source is not reproduced here

Licensed MIT-0

The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

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. yesterday First seen · 81 lines · 237 tokens per session scan A 85ed7ad40467

Subscribe to this mod's changes

agent-debugger is an agent published in the GitHub repository aws-samples/sample-autonomous-cloud-coding-agents (132 stars, last pushed 3d ago), licensed MIT-0. It adds 237 tokens to every session and 801 once invoked, about $0.0012 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.