manage-error-debugging

A command manages an automated watcher that monitors error reports and starts debugging workflows when configured conditions are met.

In plain words
What is it for?
Use it with the foundation configuration to control the error-debugging watcher and view its recent logs.
Why use it?
It provides simple controls for checking, starting, stopping, restarting, and inspecting the watcher instead of managing its process manually.

Skill for Claude CodeCodexCursor

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

Made for: Claude Code, Codex, Cursor.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,172 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% 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.00012 $0.01172
Opus 5 $0.00006 $0.00586
Sonnet 5 $0.00002 $0.00234
Haiku 4.5 $0.00001 $0.00117

Measured yesterday against content hash b1cbd939ef3a, 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 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.

Origin

This is a copy

94% identical to manage-error-debugging — 7 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.

.cursor/skills/manage-error-debugging/SKILL.md · 183 lines

How it starts

The opening of the file, as written. The whole thing — 183 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)"
  3. Stop process:

    • Send TERM signal to process
    • Wait up to 5 seconds for graceful shutdown
    • If still running, send KILL signal
    • Remove PID file
    • Output: "Stopped error debugging watcher (PID: {pid})"

Read the full file on GitHub · 183 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. yesterday First seen · 183 lines · 12 tokens per session scan A b1cbd939ef3a

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens