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/Yassinello/claude-plugin-prd-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/yassinello/claude-plugin-prd-workflow/debugging)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/debugging"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/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/commands/yassinello/claude-plugin-prd-workflow/debugging"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/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.00010 | $0.04042 |
| Opus 5.5 | $0.00004 | $0.01617 |
| Sonnet 5.5 | $0.00002 | $0.00808 |
| Haiku 4.5 | $0.00001 | $0.00404 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 699 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Command
Fast, systematic debugging with hypothesis testing and team knowledge capture, with optional worktree isolation.
Purpose
Transform chaotic debugging into efficient investigation with:
- Quick triage and pattern recognition
- Known issues search before reinventing solutions
- Hypothesis-driven testing
- Team knowledge documentation
NEW in v0.4.4: Automatic context detection - run from Main OR from worktree directly!
v0.4.3: Support for worktree isolation with --worktree flag for debugging sessions requiring code modifications.
Context Detection (Auto)
The /debugging command automatically detects where you run it from:
From Main Repository
# Working directory: ~/Documents/watchora
$ /debugging "Check API timeout"
→ Behavior: Read-only investigation on Main (default)
→ Optional: Add --worktree for code modifications
From Debug Worktree
# Working directory: ~/Documents/watchora/worktrees/debug
$ /debugging "Check API timeout"
→ Behavior: Automatically uses worktree (no --worktree needed!)
→ Syncs, locks, creates branch, works in current directory
Key Point: If you have a dedicated Cursor window open on worktrees/debug/, you can use /debugging directly from there!
Usage
# From Main: Investigate on Main (read-only, quick)
/debugging "Check why API returns 500"
# From Main: With worktree isolation (modifications needed)
/debugging "Memory leak in WebSocket handler" --worktree
# From Worktree: Auto-detects worktree context
cd worktrees/debug/
/debugging "Memory leak issue" # Automatically uses worktree!
# Manage active session (works from anywhere)
/debugging --resolve # Complete and document
/debugging --abort # Cancel session
/debugging --status # Show current status
/debugging --pause # Pause session
/debugging --resume # Resume paused session
# Migrate from Main to worktree
/debugging --to-worktree # Move current session to worktree
# List past sessions
/debugging --list # Show all debug sessions
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 · 699 lines · 10 tokens per session scan A 148649bdd5f3
debugging is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 11mo ago), licensed MIT. It adds 10 tokens to every session and 4,042 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
lint
The canonical linter per ecosystem over your changes: findings are diagnoses you judge, fix, or explain.
verify
A command that independently checks the factual claims and file-and-line references in an agent’s most recent response. It reports whether each claim is confirmed, outdated, missing, or unsupported.
sm-refit
Run slop-mop's one-time onboarding remediation rail for this repository.
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.