A maintenance-task planning command that turns a chore description into a planning record and task list. A chore is housekeeping work that should not change product behavior.

Use it to plan one maintenance task, such as cleanup or repository housekeeping, before implementation.

It keeps maintenance work bounded and explains why it is needed without inventing details.

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/chore.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/chore/github.svg)](https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/chore)

Your own site

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/chore"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/chore/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/chore"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/chore.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 2,181 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.02181
Opus 5.5	$0.00000	$0.00872
Sonnet 5.5	$0.00000	$0.00436
Haiku 4.5	$0.00000	$0.00218

Measured 11d ago against content hash d23246758f1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chore 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/chore.md · 157 lines

How it starts

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

Chore — Plan a maintenance or housekeeping task.

Variables

$ARGUMENTS — description of the chore to plan.

Purpose

Plan one maintenance or housekeeping task — no behavior change, tests incidental. Output is a block record (planning/blocks/<BlockID>.json) plus a task list (planning/<BlockID>/tasks.json), feeding into lean /sdlc-task.

Distinct from /ticket: tickets change behavior, so tests are required and Acceptance Criteria are non-negotiable. Chores do not — but they still state a why and a boundary. For multi-block work use /plan instead.

Instructions

If $ARGUMENTS is not provided, stop and ask the user to describe the chore.
Plan-quality floor — clarify, don't fabricate. If filling a load-bearing element (which files to change, the scope boundary, or the why) would require inventing a fact you cannot ground in $ARGUMENTS, CLAUDE.md, planning/context.md, or the repo — stop and ask a targeted question rather than write a plausible-looking guess. A chore whose why is "it seemed untidy" is a chore nobody can evaluate six months later, which is exactly the gap D65 exists to close.
Research the codebase: read CLAUDE.md, planning/context.md, then the files directly relevant to the chore.

3a. Establish ground truth, chore-sized. Run the gated checks (planning/harness.json → validation.checks[]) before changing anything, and record which pass. A chore's whole promise is "no behaviour change," and you cannot claim that against a baseline you never took — a check that was already red gets attributed to this chore, and one that was already green gets read as proof the chore was safe.

3b. The floor, chore-sized. Two questions, a sentence each:

Is this a deletion? Ask it explicitly, even when the chore was framed as a change. Removing dead or superseded surface is usually cheaper than tidying it, and it is the version of the work nobody proposes. Check whether the thing has any remaining caller before assuming it must be kept: one rg -L settles it.
What else touches these files? One grep. A housekeeping change with a wide blast radius is not housekeeping, and this is where that gets noticed rather than at merge.

Read the full file on GitHub · 157 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 · 157 lines · 0 tokens per session scan A d23246758f1e

Subscribe to this mod's changes

chore 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 2,181 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

chore next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
chorebredmond1019/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