debug-toolbar: Command for Claude Code

.claude/commands/implement.md

implement is a command for Claude Code from JacobCoffee/debug-toolbar. It costs 7 tokens per session (1,178 once invoked), scanned A, original, MIT.

An implementation workflow that turns a product requirements document into code while following patterns already used in the project.

In plain words
What is it for?
It is for implementing planned features, reusing established project patterns, keeping changes incremental, and designing code that is easier to test.
Why use it?
It reduces guesswork by loading the requirements, related research, and similar code before implementation, then breaking the work into smaller tasks.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is JacobCoffee/debug-toolbar's own configuration. It tells Claude Code how to work on debug-toolbar itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything debug-toolbar configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/JacobCoffee/debug-toolbar/main/.claude/commands/implement.md
Clone the repo
git clone --depth 1 https://github.com/JacobCoffee/debug-toolbar

Made for: Claude Code.

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.

agentmods badge for implement

README.md
[![agentmods](https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/implement.svg)](https://agentmods.dev/commands/jacobcoffee/debug-toolbar/implement)
Your own site
<a href="https://agentmods.dev/commands/jacobcoffee/debug-toolbar/implement"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/implement.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00007 $0.01178
Opus 5 $0.00003 $0.00589
Sonnet 5 $0.00001 $0.00236
Haiku 4.5 $0.00001 $0.00118

Measured 2d ago against content hash 209462c6e525, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

implement 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.

.claude/commands/implement.md · 230 lines

How it starts

The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Intelligent Implementation Workflow

You are implementing the feature from PRD: $ARGUMENTS

Pre-Implementation Checklist

  1. Load PRD from specs/active/{slug}/prd.md
  2. Load pattern analysis from specs/active/{slug}/patterns/
  3. Read similar implementations identified in PRD
  4. Consult pattern library at specs/guides/patterns/

Critical Rules

  1. PATTERN COMPLIANCE - Follow patterns from similar features
  2. NO OVER-ENGINEERING - Only implement what's in the PRD
  3. TYPE SAFETY - Use PEP 604 (T | None), future annotations
  4. TEST READY - Design for testability
  5. INCREMENTAL - Commit logically, not at the end

Phase 1: Context Loading

Load intelligence context:

# Verify PRD exists
cat specs/active/{slug}/prd.md

# Load patterns
cat specs/active/{slug}/patterns/analysis.md

# Load research
cat specs/active/{slug}/research/plan.md

Read similar implementations:

  • Read files identified in PRD's "Similar Implementations" section
  • Extract exact patterns to follow

Output: "✓ Phase 1 complete - Context loaded"


Phase 2: Implementation Planning

Break down into atomic tasks:

For each file to create/modify:

  1. Identify dependencies
  2. Plan implementation order
  3. Note patterns to apply

Update workspace:

echo "## Implementation Plan" >> specs/active/{slug}/tmp/progress.md

Output: "✓ Phase 2 complete - Implementation planned"


Phase 3: Core Implementation

Follow the Panel pattern if creating a panel:

"""Panel implementation."""

from __future__ import annotations

from typing import TYPE_CHECKING, Any, ClassVar

from debug_toolbar.core.panel import Panel

if TYPE_CHECKING:
    from debug_toolbar.core.context import RequestContext


class NewPanel(Panel):
    """Description."""

    panel_id: ClassVar[str] = "NewPanel"
    title: ClassVar[str] = "New Panel"
    template: ClassVar[str] = "panels/new_panel.html"
    has_content: ClassVar[bool] = True

    async def generate_stats(self, context: RequestContext) -> dict[str, Any]:
        """Generate statistics."""
        return {}

Read the full file on GitHub · 230 lines

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 · 230 lines · 7 tokens per session scan A 209462c6e525

Subscribe to this mod's changes

implement is a command published in the GitHub repository JacobCoffee/debug-toolbar (7 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 1,178 once invoked, about $0.0000 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.