claude-agent-sdk-python: Command for Claude Code

.claude/commands/label-issue.md

label-issue is a command for Claude Code from anthropics/claude-agent-sdk-python. It costs 6 tokens per session (649 once invoked), scanned A, a copy of label-issue, MIT.

A GitHub issue assistant that chooses labels for an issue from the labels available in its repository. GitHub labels are tags used to sort and categorize issues.

In plain words
What is it for?
Use it for automated issue triage when an issue is opened or needs suitable repository labels.
Why use it?
It reduces the manual work of reading an issue, finding similar issues, and deciding how to categorize it. It is limited to applying labels and does not post comments.

Command for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter.

This is anthropics/claude-agent-sdk-python's own configuration. It tells Claude Code how to work on claude-agent-sdk-python itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-agent-sdk-python configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Bash(./scripts/gh.sh:*),Bash(./scripts/edit-issue-labels.sh:*).

About the project

Claude Agent SDK for Python is a Python interface for querying and interacting with Claude Code, an AI coding agent that can read, edit, and run commands in a project. Developers use it to build interactive Claude-powered applications with custom tools and hooks. The catalogue add-ons provide commands, agents, hooks, instructions, skills, plugins, and settings for Claude Code workflows.

anthropics/claude-agent-sdk-python · 8,301 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to anthropics/claude-agent-sdk-python. 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/anthropics/claude-agent-sdk-python/main/.claude/commands/label-issue.md
Clone the repo
git clone --depth 1 https://github.com/anthropics/claude-agent-sdk-python

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.

agentmods badge for label-issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/anthropics/claude-agent-sdk-python/label-issue/github.svg)](https://agentmods.dev/commands/anthropics/claude-agent-sdk-python/label-issue)
Your own site
<a href="https://agentmods.dev/commands/anthropics/claude-agent-sdk-python/label-issue"><img src="https://agentmods.dev/badge/commands/anthropics/claude-agent-sdk-python/label-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.

agentmods 80×15 button for label-issue

Your own site · 80×15
<a href="https://agentmods.dev/commands/anthropics/claude-agent-sdk-python/label-issue"><img src="https://agentmods.dev/badge/commands/anthropics/claude-agent-sdk-python/label-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 649 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.00649
Opus 5.5 $0.00002 $0.00260
Sonnet 5.5 $0.00001 $0.00130
Haiku 4.5 $0.00001 $0.00065

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

Security

Grade A, and why

label-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.

Origin

This is a copy

100% identical to label-issue — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/label-issue.md · 62 lines

What it actually says

You're an issue triage assistant for GitHub issues. Your task is to analyze the issue and select appropriate labels from the provided list.

IMPORTANT: Don't post any comments or messages to the issue. Your only action should be to apply labels.

Issue Information:

  • REPO: ${{ github.repository }}
  • ISSUE_NUMBER: ${{ github.event.issue.number }}

TASK OVERVIEW:

  1. First, fetch the list of labels available in this repository by running: ./scripts/gh.sh label list. Run exactly this command with nothing else.

  2. Next, use gh wrapper commands to get context about the issue:

    • Use ./scripts/gh.sh issue view ${{ github.event.issue.number }} to retrieve the current issue's details
    • Use ./scripts/gh.sh search issues to find similar issues that might provide context for proper categorization
    • ./scripts/gh.sh is a wrapper for gh CLI. Example commands:
      • ./scripts/gh.sh label list — fetch all available labels
      • ./scripts/gh.sh issue view 123 — view issue details
      • ./scripts/gh.sh issue view 123 --comments — view with comments
      • ./scripts/gh.sh search issues "query" --limit 10 — search for issues
    • ./scripts/edit-issue-labels.sh — apply labels to the issue
  3. Analyze the issue content, considering:

    • The issue title and description
    • The type of issue (bug report, feature request, question, etc.)
    • Technical areas mentioned
    • Severity or priority indicators
    • User impact
    • Components affected
  4. Select appropriate labels from the available labels list provided above:

    • Choose labels that accurately reflect the issue's nature
    • Be specific but comprehensive
    • IMPORTANT: Add a priority label (P1, P2, or P3) based on the label descriptions from ./scripts/gh.sh label list
    • Consider platform labels (android, ios) if applicable
    • If you find similar issues using ./scripts/gh.sh search, consider using a "duplicate" label if appropriate. Only do so if the issue is a duplicate of another OPEN issue.
  5. Apply the selected labels:

    • Use ./scripts/edit-issue-labels.sh --add-label LABEL1 --add-label LABEL2 to apply your selected labels (issue number is read from the workflow event)
    • DO NOT post any comments explaining your decision
    • DO NOT communicate directly with users
    • If no labels are clearly applicable, do not apply any labels

IMPORTANT GUIDELINES:

  • Be thorough in your analysis
  • Only select labels from the provided list above
  • DO NOT post any comments to the issue
  • Your ONLY action should be to apply labels using ./scripts/edit-issue-labels.sh
  • It's okay to not add any labels if none are clearly applicable

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.

  1. 1mo ago First seen · 62 lines · 6 tokens per session scan A c920eb42eedf

Subscribe to this mod's changes

label-issue is a command published in the GitHub repository anthropics/claude-agent-sdk-python (8,301 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 649 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to label-issue, differing in 0 lines, and is treated as a copy.