foundation: Skill for Cursor

.cursor/skills/manage-error-debugging/SKILL.md

manage-error-debugging is a skill for Cursor from markmhendrickson/foundation. It costs 12 tokens per session (1,172 once invoked), scanned A, a copy of manage-error-debugging, MIT.

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 Cursor

Written for Cursor: installed under .cursor/.

This is markmhendrickson/foundation's own configuration. It tells Cursor how to work on foundation itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything foundation configures →

Reuse

Borrowing it

Nothing to install: this file belongs to markmhendrickson/foundation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/markmhendrickson/foundation/main/.cursor/skills/manage-error-debugging/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/foundation

Made for: Cursor.

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/foundation/manage-error-debugging/github.svg)](https://agentmods.dev/skills/markmhendrickson/foundation/manage-error-debugging)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/foundation/manage-error-debugging"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/manage-error-debugging/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for manage-error-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/markmhendrickson/foundation/manage-error-debugging"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/manage-error-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00012 $0.01172
Opus 5.5 $0.00005 $0.00469
Sonnet 5.5 $0.00002 $0.00234
Haiku 4.5 $0.00001 $0.00117

Measured 1mo ago against content hash b1cbd939ef3a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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

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. 1mo ago 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 2mo ago), licensed MIT. It adds 12 tokens to every session and 1,172 once invoked, about $0.0000 per session on Opus 5.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

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens