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.
git clone --depth 1 https://github.com/jpeseWang/solo-dev-workflowWrote 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/commands/jpesewang/solo-dev-workflow/debug)<a href="https://agentmods.dev/commands/jpesewang/solo-dev-workflow/debug"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/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/commands/jpesewang/solo-dev-workflow/debug"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/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.00000 | $0.01243 |
| Opus 5.5 | $0.00000 | $0.00497 |
| Sonnet 5.5 | $0.00000 | $0.00249 |
| Haiku 4.5 | $0.00000 | $0.00124 |
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug
Reproduce first, isolate second, fix the root cause third — and leave a test that would have caught it.
The rest of the workflow covers the happy path. This is for when something is broken, which is most days. It exists because debugging is where an assistant most reliably goes wrong: it reads the symptom, pattern-matches a plausible cause, changes something, and the symptom disappears for a reason nobody understands.
The rule that makes this command worth running: no fix before a reproduction.
Input: the symptom. An error message, a stack trace, a failing test name, or a description of wrong behaviour. If it's empty, ask what's broken and how you'd see it.
Step 1 — Reproduce it
Before reading any code, get a command that fails on demand:
# the failing test, if there is one
<test command> -t "<name>"
# or the exact steps/command that produce the wrong behaviour
Write down the expected and the actual, concretely. "It crashes" is not a reproduction.
GET /api/cart with an empty cart returns 500, expected 200 with [] is.
If you cannot reproduce it:
- Say so plainly. Do not proceed to fix it anyway.
- Ask for what's missing: the input that triggers it, the environment, the exact error text, a log line with a timestamp.
- A bug you cannot reproduce is a bug you cannot verify you fixed. That is the whole problem.
Step 2 — Locate the failure, don't guess it
Narrow mechanically. Prefer evidence over inference:
# what changed recently around here?
git log --oneline -20 -- <suspect path>
git log -S"<symbol from the trace>" --oneline # when did this string appear/disappear?
# did it used to work? let git find the commit
git bisect start <bad-sha> <good-sha>
Read the actual stack trace top to bottom. Add a temporary log or breakpoint at the boundary between "state is still correct" and "state is now wrong" — the bug lives in that gap.
State a hypothesis explicitly before testing it: "I think cart.items is undefined because the
API returns null for an empty cart and the destructure assumes an array." A hypothesis you
can't state in one sentence isn't a hypothesis yet.
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.
- 2mo ago First seen · 125 lines · 0 tokens per session scan A b10dd4de88dd
debug is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,243 tokens. 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-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.