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/implement.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/implement)<a href="https://agentmods.dev/commands/jacobcoffee/debug-toolbar/implement"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/implement/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/jacobcoffee/debug-toolbar/implement"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/implement.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.00007 | $0.01178 |
| Opus 5.5 | $0.00003 | $0.00471 |
| Sonnet 5.5 | $0.00001 | $0.00236 |
| Haiku 4.5 | $0.00001 | $0.00118 |
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 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 — 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
- Load PRD from
specs/active/{slug}/prd.md - Load pattern analysis from
specs/active/{slug}/patterns/ - Read similar implementations identified in PRD
- Consult pattern library at
specs/guides/patterns/
Critical Rules
- PATTERN COMPLIANCE - Follow patterns from similar features
- NO OVER-ENGINEERING - Only implement what's in the PRD
- TYPE SAFETY - Use PEP 604 (
T | None), future annotations - TEST READY - Design for testability
- 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:
- Identify dependencies
- Plan implementation order
- 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 {}
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 · 230 lines · 7 tokens per session scan A 209462c6e525
implement is a command published in the GitHub repository JacobCoffee/debug-toolbar (8 stars, last pushed 17d ago), licensed MIT. It adds 7 tokens to every session and 1,178 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-09-04.
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.
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.
fix
Universal debugging and fix application with semantic code analysis.