A planning command for turning one small bug fix or targeted behavior change into a work ticket. It creates acceptance criteria, a record of the work block, and a task list, with tests required for the changed behavior.

Use it to plan a focused bug fix or enhancement that needs code changes and new or modified tests.

It prevents small changes from starting without a clear definition of correct, observable behavior. It also distinguishes behavior changes from maintenance chores and larger multi-part plans.

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

Your own site

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/ticket"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/ticket/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/ticket"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/ticket.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 3,236 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.03236
Opus 5.5	$0.00000	$0.01294
Sonnet 5.5	$0.00000	$0.00647
Haiku 4.5	$0.00000	$0.00324

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

Security

Grade A, and why

ticket 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/ticket.md · 218 lines

How it starts

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

Ticket — Plan a small behavior-change with observable Acceptance Criteria.

Variables

$ARGUMENTS — description of the bug fix, enhancement, or small behavior-change to implement.

Purpose

Plan one small, well-scoped behavior-change — a bug fix or targeted enhancement that requires new or modified tests. Output is a block record (planning/blocks/<BlockID>.json) plus a task list (planning/<BlockID>/tasks.json), feeding directly into lean /sdlc-task.

A ticket is the one producer that writes both records at author time: it is a one-off with no downstream block waiting on its code, so there is nothing to defer (D65).

Distinct from /chore: chores are maintenance — no behavior change, tests incidental. Tickets are behavior-changing: tests required, Acceptance Criteria non-negotiable. For multi-block work use /plan instead.

Instructions

If $ARGUMENTS is not provided, stop and ask the user to describe the bug or change.
Plan-quality floor — clarify, don't fabricate. If filling a load-bearing element (which files to change, what the observable correct behavior is, an Acceptance Criterion, 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. An honest "I need X to write the AC" beats a confident invention.
Research the codebase: read CLAUDE.md, planning/context.md, then the files directly relevant to the change.

3a. Reproduce it, or observe the current behaviour, before writing a single Acceptance Criterion. This is the ticket-sized version of establishing ground truth and it is the highest-value minute in this command.

Bug fix: make it fail. Run the failing case and record the actual output or error text. A ticket written from a described bug fixes the description, not the bug — and the AC will describe a symptom nobody has seen.
Enhancement: run the current behaviour so the AC says what changes, not what you assume is there today.
If you cannot reproduce it, say so plainly and write that into the block record's why. Then either ask the user for the reproduction, or make the first task "reproduce and record the failing case" — do not write AC over an unobserved failure.

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

Subscribe to this mod's changes

ticket 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 3,236 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.

Project management Testing

ticket next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ticketbredmond1019/claude-sdk-rs	Command	23	1mo ago	Apache-2.0	A	0	Claude Code
prototypegrainulation/grainulator	Command	86	yesterday	MIT	A	0	Claude Code
qa-changesOpenHands/extensions	Command	176	yesterday	MIT	A	63	Claude Code
verifycloudnative-co/claude-code-starter-kit	Command	153	25d ago	MIT	A	9	Claude Code
modernize-transformfuxicodex/Fuxi	Command	3.2k	17d ago	none	A	17	Claude Code
constraintsvinvcn/addyosmani-agent-skills-zh	Command	46	17d ago	MIT	A	20	Claude Code
check-devpunt-labs/z-spec	Command	5	yesterday	MIT	A	7	Claude Code

claude-sdk-rs: Command for Claude Code