debug

A command that investigates a software problem in four phases before suggesting a fix, and saves its findings for the fixing agent.

In plain words
What is it for?
Use it to trace bugs, record evidence and suspected causes, and guide a separate fix through a documented investigation.
Why use it?
It prevents guessing at fixes before the underlying cause is understood. The written investigation gives later work a clear basis.

Command for Cursor

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 commands/kanevry/session-orchestrator/debug
Clone the repo
git clone --depth 1 https://github.com/Kanevry/session-orchestrator

Made for: Cursor.

Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 172 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00044 $0.00172
Opus 5 $0.00022 $0.00086
Sonnet 5 $0.00009 $0.00034
Haiku 4.5 $0.00004 $0.00017

Measured 2d ago against content hash b13dd9868015, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debug 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 2d 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.

.cursor/commands/debug.md · 15 lines

What it actually says

/debug

Use the Session Orchestrator command definition at commands/debug.md.

Arguments: $ARGUMENTS

Read that command file and follow it exactly. When it references $ARGUMENTS, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

Cursor has no Skill tool. When the command says to invoke a skill, Read skills/<skill-name>/SKILL.md and follow it. Supporting files (soul.md, phase docs) live in that same skills/<skill-name>/ directory.

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. 2d ago First seen · 15 lines · 44 tokens per session scan A b13dd9868015

Subscribe to this mod's changes

debug is a command published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 172 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.