Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/markmhendrickson/neotoma/debug)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/debug"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/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/neotoma/debug"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/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.00004 | $0.06801 |
| Opus 5.5 | $0.00002 | $0.02720 |
| Sonnet 5.5 | $0.00001 | $0.01360 |
| Haiku 4.5 | $0.00000 | $0.00680 |
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 }) How it starts
The opening of the file, as written. The whole thing — 988 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: debug description: Debug workflow per foundation command. triggers:
- debug
- /debug
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 · 988 lines · 4 tokens per session scan A ebf02ea699ec
debug is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 4 tokens to every session and 6,801 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
bernstein-alerts
Show active alerts from Bernstein - failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
ci-fixer
CI failures - read error, minimal fix, verify.
cratis-chronicle-cli-operations
Inspect and operate a running Chronicle server with the cratis CLI - contexts and connection resolution, machine-readable output, failed partitions, observers, event sequences, read models, projections and jobs, and the authorization discipline for replay, retry, quarantine clearing and other mutations. Use when the…
plumb-line-remediate
Use when applying findings from a plumb-line audit report — the builder has a report (or pasted findings) and wants the fixes made. Opt-in and separate from the audit, which is read-only and never fixes.
cratis-lens-browser-extension
Use the Cratis Lens browser extension against a running Cratis Arc application — building and side-loading it, what the Arc app must already serve for Lens to work, switching the active user and tenant, and executing a command or query from the popup. Use when setting Lens up, when Lens does not detect an Arc app, or…
cratis-arc-observable-query-http
Inspect a Cratis Arc observable query from a terminal with curl or another plain HTTP client — snapshot GET, waiting for the first result, Server-Sent Events streaming, and long polling, plus the exact query-string keys, status codes, and payload shape. Use when debugging or exploring an observable query without…