manage_error_debugging

manage_error_debugging is a skill for Claude Code, Codex from markmhendrickson/neotoma. It costs 10 tokens per session (1,163 once invoked), scanned A, a copy of manage-error-debugging, MIT.

A command for managing an automated watcher that monitors error-debugging work. It can start, stop, restart, inspect the status of, and show logs from the watcher.

In plain words
What is it for?
Use it to operate the error-debugging watcher in a Node.js project, including checking configuration, starting or stopping the background process, and viewing recent logs.
Why use it?
It avoids manually checking whether the monitoring process is running and where its recent output is stored.

Skill for Claude CodeCodex

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 skills/markmhendrickson/neotoma/manage_error_debugging
Any agent
npx skills add markmhendrickson/neotoma --skill manage_error_debugging
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/neotoma

Made for: Claude Code, Codex.

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 manage_error_debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/markmhendrickson/neotoma/manage_error_debugging.svg)](https://agentmods.dev/skills/markmhendrickson/neotoma/manage_error_debugging)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/manage_error_debugging"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/manage_error_debugging.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,163 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00010 $0.01163
Opus 5 $0.00005 $0.00581
Sonnet 5 $0.00002 $0.00233
Haiku 4.5 $0.00001 $0.00116

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

Security

Grade A, and why

manage_error_debugging 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 3d 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.

Origin

This is a copy

88% identical to manage-error-debugging — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/manage_error_debugging/SKILL.md · 182 lines

How it starts

The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage Error Debugging Automation

Manage the error debugging automation monitoring script (start, stop, status, logs).

Command Usage

/manage_error_debugging [action]

Actions:

  • start - Start the error debugging watcher in background
  • stop - Stop the running watcher
  • status - Check if watcher is running and show status
  • logs - Show recent logs from the watcher
  • restart - Stop and start the watcher
  • (no action) - Show status (default)

Prerequisites

  • Error debugging automation enabled in foundation-config.yaml
  • scripts/trigger_error_debug_cli.js exists and is executable
  • Node.js installed

Workflow

Action: start

  1. Check if already running:

    • Check for PID file: .cursor/error_reports/watcher.pid
    • If PID file exists, verify process is still running
    • If running, exit with message: "Error debugging watcher is already running (PID: {pid})"
  2. Verify configuration:

    • Load foundation-config.yaml
    • Check development.error_debugging.enabled === true
    • If disabled, exit with error
  3. Create necessary directories:

    • Ensure .cursor/error_reports/ exists
    • Ensure log directory exists (if configured)
  4. Start watcher in background:

    • Run: node scripts/trigger_error_debug_cli.js --watch > .cursor/error_reports/watcher.log 2>&1 &
    • Capture PID of background process
    • Write PID to .cursor/error_reports/watcher.pid
    • Output: "Started error debugging watcher (PID: {pid})"
  5. Verify start:

    • Wait 1 second
    • Check if process is still running
    • If not running, read log file and show error

Action: stop

  1. Check if running:

    • Read PID from .cursor/error_reports/watcher.pid
    • If PID file doesn't exist, exit: "Error debugging watcher is not running"
  2. Verify process exists:

    • Check if process with PID is running
    • If not running, remove stale PID file and exit: "Watcher process not found (stale PID file removed)"

Read the full file on GitHub · 182 lines

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. 3d ago First seen · 182 lines · 10 tokens per session scan A 6e1d05deec3d

Subscribe to this mod's changes

manage_error_debugging is a skill published in the GitHub repository markmhendrickson/neotoma (29 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 1,163 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to manage-error-debugging, differing in 12 lines, and is treated as a copy.