A command for carrying out tasks written in a plan file against a codebase. It can run every task or only one numbered task, after first orienting itself to the project and reading the plan.

Use it to implement planned features or maintenance work and run the validation checks relevant to the selected task.

It turns an agreed plan into scoped implementation work instead of requiring the agent to infer the work from a brief request. Running only the requested task limits unrelated changes and checks.

How bredmond1019/claude-sdk-rs configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bredmond1019/claude-sdk-rs. 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/bredmond1019/claude-sdk-rs/main/.claude/commands/implement.md

Clone the repo

git clone --depth 1 https://github.com/bredmond1019/claude-sdk-rs

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/implement/github.svg)](https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/implement)

Your own site

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/implement"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/implement"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 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,416 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01416
Opus 5.5	$0.00000	$0.00566
Sonnet 5.5	$0.00000	$0.00283
Haiku 4.5	$0.00000	$0.00142

Measured 11d ago against content hash 9e596d2716fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 11d 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 · 98 lines

How it starts

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

Implement — Execute a plan file against the codebase.

Variables

$ARGUMENTS — path to the plan file to implement, with an optional task number suffix.

Examples:

planning/<spec-slug>/tasks.md — run all tasks in the plan
planning/<spec-slug>/tasks.md 1 — run only Task 1
planning/<spec-slug>/tasks.md 3 — run only Task 3

Instructions

If $ARGUMENTS is not provided, stop and ask the user for the plan file path.
Parse $ARGUMENTS: split on the last space. If the trailing token is a number, treat it as the task number to run in isolation; the remainder is the plan file path. If no number is present, run all tasks.
Run /prime to orient to the codebase before touching any code.
Read the plan file in full.
THINK HARD about the plan: understand the goal, relevant files, and the target task(s) before writing anything.
If a task number was given: execute only that numbered task from the Step-by-Step Tasks section. Skip all others. After completing it, run only the validation checks directly relevant to that task (a subset of the project's checks in planning/harness.json / the spec's ## Validation Commands). Do NOT run the full validation suite — that is reserved for when all tasks are complete.
If no task number was given: execute every Step-by-Step task in order, top to bottom.
- Follow existing code patterns and conventions (see CLAUDE.md).
- Read CLAUDE.md and planning/context.md and enforce the project's standing rules — do not assume any stack, locale-parity, narrative, or content-layout rule unless written there.
- Universal harness rules: no fabricated metrics/quotes (verify model ids / package names via the claude-api skill, not memory), no emoji, every change ships with tests.
After all tasks are complete (full run only), run the spec's ## Validation Commands exactly as written. If the spec has none, run the project's checks from planning/harness.json (validation.checks[]); if that is absent too, stop and ask the user for the validation commands.
If validation fails, fix the failure before reporting.
Record the completed work (see Record).

Read the full file on GitHub · 98 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.

11d ago First seen · 98 lines · 0 tokens per session scan A 9e596d2716fa

Subscribe to this mod's changes

implement is a command published in the GitHub repository bredmond1019/claude-sdk-rs (23 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,416 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-10-26.

Planning Project management

implement next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
implementbredmond1019/claude-sdk-rs	Command	23	1mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

claude-sdk-rs: Command for Claude Code