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.
npx skills add markmhendrickson/ateles --skill manage-error-debugginggit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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.
[](https://agentmods.dev/skills/markmhendrickson/ateles/manage-error-debugging)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/manage-error-debugging"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/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.
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/manage-error-debugging"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/manage-error-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00012 | $0.01201 |
| Opus 5.5 | $0.00005 | $0.00480 |
| Sonnet 5.5 | $0.00002 | $0.00240 |
| Haiku 4.5 | $0.00001 | $0.00120 |
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.
This is a copy
91% 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.
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 backgroundstop- Stop the running watcherstatus- Check if watcher is running and show statuslogs- Show recent logs from the watcherrestart- Stop and start the watcher- (no action) - Show status (default)
Prerequisites
- Error debugging automation enabled in
foundation-config.yaml scripts/trigger_error_debug_cli.jsexists and is executable- Node.js installed
Workflow
Action: start
-
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})"
- Check for PID file:
-
Verify configuration:
- Load
foundation-config.yaml - Check
development.error_debugging.enabled === true - If disabled, exit with error
- Load
-
Create necessary directories:
- Ensure
.cursor/error_reports/exists - Ensure log directory exists (if configured)
- Ensure
-
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})"
- Run:
-
Verify start:
- Wait 1 second
- Check if process is still running
- If not running, read log file and show error
Action: stop
-
Check if running:
- Read PID from
.cursor/error_reports/watcher.pid - If PID file doesn't exist, exit: "Error debugging watcher is not running"
- Read PID from
-
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)"
-
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})"
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.
- 1mo ago First seen · 182 lines · 12 tokens per session scan A 0b2d04eea044
manage-error-debugging is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,201 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to manage-error-debugging, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
doctor
Diagnose Polisade Orchestrator project health.
defect
A command for registering a software defect, meaning behavior that does not work as intended, and creating a task to fix it. The defect and its fix task receive tracked IDs and are stored in the project's backlog and task folders.
massgen-log-analyzer
Run MassGen experiments and analyze logs using automation mode, logfire tracing, and SQL queries. Use this skill for performance analysis, debugging agent behavior, evaluating coordination patterns, and improving the logging structure, or whenever an ANALYSISREPORT.md is needed in a log directory.
serena
This skill provides symbol-level code understanding and navigation using Language Server Protocol (LSP). Enables IDE-like capabilities for finding symbols, tracking references, and making precise code edits at the symbol level.
file-search
This skill should be used when agents need to search codebases for text patterns or structural code patterns. Provides fast search using ripgrep for text and ast-grep for syntax-aware code search.
config-manager
Inspect and safely update Kabot configuration, model/memory/provider settings, channel account policies, allowlists, and related status or log evidence when debugging why a setting or runtime behavior is wrong.