What is debug_pending_errors?

A command for investigating errors that are still waiting or unresolved.

Use it when code has errors that have not yet been diagnosed or fixed.

It gives an agent a focused way to work through pending errors instead of leaving them unchecked.

debug_pending_errors — Command by markmhendrickson

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 commands/markmhendrickson/neotoma/debug_pending_errors

Clone the repo

git clone --depth 1 https://github.com/markmhendrickson/neotoma

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 13 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00013
Opus 5	$0.00000	$0.00006
Sonnet 5	$0.00000	$0.00003
Haiku 4.5	$0.00000	$0.00001

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

Security

Grade A, and why

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

.cursor/commands/debug_pending_errors.md · 1 lines

What it actually says

../../foundation/agent_instructions/cursor_commands/debug_pending_errors.md

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.

2d ago First seen · 1 lines · 0 tokens per session scan A 5032d532f7e4

Subscribe to this mod's changes

debug_pending_errors is a command published in the GitHub repository markmhendrickson/neotoma (29 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 13 tokens. 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.

Debugging ai-agents entity-resolution event-sourcing mcp privacy-first provenance

debug_pending_errors

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

spec

add-business-rule

add-concept

remember

pm2-start

pm2-restart