Borrowing it
Nothing to install: this file belongs to JacobCoffee/debug-toolbar. 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/JacobCoffee/debug-toolbar/main/.claude/commands/prd.mdgit clone --depth 1 https://github.com/JacobCoffee/debug-toolbarWrote 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/jacobcoffee/debug-toolbar/prd)<a href="https://agentmods.dev/commands/jacobcoffee/debug-toolbar/prd"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/prd.svg" alt="Measured on agentmods" 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.01523 |
| Opus 5 | $0.00005 | $0.00762 |
| Sonnet 5 | $0.00002 | $0.00305 |
| Haiku 4.5 | $0.00001 | $0.00152 |
Grade A, and why
prd 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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligent PRD Creation Workflow
You are creating a Product Requirements Document for: $ARGUMENTS
Intelligence Layer (ACTIVATE FIRST)
Before starting checkpoints:
- Read MCP Strategy: Load
.claude/mcp-strategy.mdfor tool selection - Learn from Codebase: Read 3-5 similar implementations
- Assess Complexity: Determine simple/medium/complex
- Adapt Workflow: Adjust checkpoint depth
Critical Rules
- CONTEXT FIRST - Read existing patterns before planning
- NO CODE MODIFICATION - Planning only
- PATTERN LEARNING - Identify 3-5 similar features
- ADAPTIVE DEPTH - Simple=6, Medium=8, Complex=10+ checkpoints
- RESEARCH GROUNDED - Minimum 2000+ words research
- COMPREHENSIVE PRD - Minimum 3200+ words
Checkpoint 0: Intelligence Bootstrap
Load project intelligence:
- Read
CLAUDE.md - Read
specs/guides/patterns/README.md - Read
.claude/mcp-strategy.md
Learn from existing implementations:
For panels: Read files in src/debug_toolbar/core/panels/
For integrations: Read files in src/debug_toolbar/litestar/
For extras: Read files in src/debug_toolbar/extras/
Assess complexity:
- Simple: Config change, bug fix, single file → 6 checkpoints
- Medium: New panel, API endpoint, 2-3 files → 8 checkpoints
- Complex: New integration, architecture change, 5+ files → 10+ checkpoints
Output: "✓ Checkpoint 0 complete - Complexity: [level], Checkpoints: [count]"
Checkpoint 1: Pattern Recognition
Identify similar implementations:
- Search for related patterns in
src/debug_toolbar/ - Read at least 3 similar files
- Extract naming patterns
- Note testing patterns from
tests/
Document:
## Similar Implementations
1. `src/path/to/similar1.py` - Description
2. `src/path/to/similar2.py` - Description
3. `src/path/to/similar3.py` - Description
## Patterns Observed
- Class structure: ...
- Naming conventions: ...
- Error handling: ...
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.
- 2d ago First seen · 258 lines · 10 tokens per session scan A dd69d33f5ccc
prd is a command published in the GitHub repository JacobCoffee/debug-toolbar (7 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 1,523 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.