Borrowing it
Nothing to install: this file belongs to utensils/claudette. 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/utensils/claudette/main/.claude/commands/implement-issue.mdgit clone --depth 1 https://github.com/utensils/claudetteWrote 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/utensils/claudette/implement-issue)<a href="https://agentmods.dev/commands/utensils/claudette/implement-issue"><img src="https://agentmods.dev/badge/commands/utensils/claudette/implement-issue/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/utensils/claudette/implement-issue"><img src="https://agentmods.dev/badge/commands/utensils/claudette/implement-issue.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.00965 |
| Opus 5.5 | $0.00000 | $0.00386 |
| Sonnet 5.5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
implement-issue 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement the changes described in one or more GitHub issues passed via $ARGUMENTS.
Arguments
$ARGUMENTS accepts one or more GitHub issue numbers in any of these formats:
123— single issue#123 #456— multiple with hash prefixes123,456,789— comma-separated#123, #456— comma-separated with hashes
Parsing rule: strip all # characters, then split on commas and/or whitespace to extract individual issue numbers.
Steps
-
Fetch the issues — Get the full details for each issue:
- Parse
$ARGUMENTSusing the rule above to extract all issue numbers - For each issue number, run
gh issue view <number> --json title,body,labels,comments - Read all titles, descriptions, and comments carefully for every issue
- Parse
-
Understand the context — Research the codebase before making changes:
- Identify which domains, files, and systems are affected across all issues
- Read the relevant source files to understand the current behavior
- Check
docs/for any existing documentation on the affected areas - Review related tests to understand expected behavior and edge cases
- If any issue references other issues or PRs, fetch those for additional context
- When working with multiple issues, identify shared concerns, overlapping files, and dependencies between the issues
-
Ask clarifying questions — Before implementing, check for ambiguity:
- If any issue is underspecified, missing acceptance criteria, or has multiple valid interpretations, stop and ask the user for clarification
- If the combined scope seems larger than expected, confirm the approach before proceeding
- If there are architectural decisions to make, present the options with trade-offs
- When working with multiple issues, flag any conflicts or contradictions between issue requirements
-
Plan the implementation — Outline the approach:
- Enter plan mode and draft a step-by-step implementation plan
- Plan a single unified implementation that addresses all issues cohesively
- Identify all files that need to be created or modified
- Note any migrations, new dependencies, or configuration changes required
- Call out where issue requirements interact or depend on each other
- Call out risks or areas that need extra care
- Wait for the user to approve the plan before proceeding
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 · 69 lines · 0 tokens per session scan A 5336d74735ad
implement-issue is a command published in the GitHub repository utensils/claudette (83 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 965 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-30.
Other commands, from other repositories
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
next
Suggest the most likely next workflow action based on current context.
afe
Evaluate feature - code review or comparison (shortcut for feature-eval).
afs
Start feature [agents...] - create workspace and begin implementation (shortcut for feature-start).
afo
Open feature worktree in terminal and start agent (shortcut for feature-open).