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.
curl -O https://raw.githubusercontent.com/markmhendrickson/foundation/main/.cursor/skills/debug/SKILL.mdgit clone --depth 1 https://github.com/markmhendrickson/foundationWrote 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/foundation/debug)<a href="https://agentmods.dev/skills/markmhendrickson/foundation/debug"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/debug/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/foundation/debug"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/debug.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.00008 | $0.06776 |
| Opus 5.5 | $0.00003 | $0.02710 |
| Sonnet 5.5 | $0.00002 | $0.01355 |
| Haiku 4.5 | $0.00001 | $0.00678 |
Grade A, and why
debug scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
remoteUrl = execSync('git remote get-url origin', { cwd: repoPath }) This is a copy
100% identical to debug — 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.
How it starts
The opening of the file, as written. The whole thing — 981 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Command
Purpose
Check for pending error reports and debug/resolve them. Supports cross-repo error queue checking for sibling repositories. Also manages the error debugging automation watcher.
Command Usage
/debug [action|target-repo-name]
Modes of Operation:
The command operates in two modes based on the first argument:
1. Watcher Management Mode
If the first argument is a watcher management action (start, stop, status, logs, restart), manage the error debugging automation watcher:
/debug start # Start the error debugging watcher
/debug stop # Stop the running watcher
/debug status # Check watcher status
/debug logs # Show watcher logs
/debug restart # Restart the watcher
2. Error Debugging Mode (Default)
If the first argument is not a watcher action (or no arguments provided), check and debug pending errors:
/debug # Check current repo's pending errors (default)
/debug neotoma # Check sibling repo's pending errors
/debug personal-project # Check another sibling repo
Note: To check watcher status, use /debug status. The default behavior (no arguments) checks for pending errors in the current repository.
Parameters:
action(optional): Watcher management action (start,stop,status,logs,restart)- If provided, manages the error debugging automation watcher
- If omitted: Defaults to error debugging mode (check pending errors)
target-repo-name(optional): Name of sibling repository to check for pending errors- Must be a sibling repository (shares same parent directory)
- Only used if first argument is not a watcher action
Examples:
# Watcher management
/debug start # Start watcher
/debug status # Check watcher status
/debug logs # View watcher logs
/debug stop # Stop watcher
# Error debugging
/debug # Check current repo's pending errors
/debug neotoma # Check sibling repo's pending errors
/debug --list-only # List errors without debugging
/debug --all --auto # Process all errors automatically
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 · 981 lines · 8 tokens per session scan A 532197230375
debug is a skill published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 6,776 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). It is 100% identical to debug, differing in 7 lines, and is treated as a copy.
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…
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.
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…
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…
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.
ci-fixer
CI failures - read error, minimal fix, verify.