A command that retrieves a GitHub issue, creates a branch for it from the latest integration branch, and provides the issue details as working context. A GitHub issue is a tracked task, bug report, or request.

Use it to begin work on a numbered issue, choosing a bug or feature branch name from its labels.

It turns an issue number into a prepared coding task and prevents work from starting on closed issues without explicit approval.

issue — Command for Claude Code by andrei-isvoran96/claude-skill-lab

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/andrei-isvoran96/claude-skill-lab

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/andrei-isvoran96/claude-skill-lab/issue/github.svg)](https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/issue)

Your own site

<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/issue"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/issue"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/issue.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 792 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.00792
Opus 5.5	$0.00000	$0.00317
Sonnet 5.5	$0.00000	$0.00158
Haiku 4.5	$0.00000	$0.00079

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

Security

Grade A, and why

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 2mo 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.

commands/issue.md · 64 lines

How it starts

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

Pick up a GitHub issue: fetch its title/body/labels, create a properly-named branch from origin/<BASE_BRANCH>, check it out, and surface the issue body as context.

Arguments

This command accepts a GitHub issue number as $ARGUMENTS. Example: /issue 207

Steps

Validate the argument. If $ARGUMENTS is empty, not a positive integer, or contains anything other than digits, ask the user to pass a numeric issue number and stop. Do NOT call gh with bogus input.
Fetch the issue. Run a single gh call to pull everything you need:
```
gh issue view $ARGUMENTS --json number,title,body,labels,state,url
```
If gh errors (issue doesn't exist, repo not configured, not authenticated), surface the error verbatim and stop.
Refuse to work on a closed issue. If state is CLOSED, warn the user, print the URL, and stop unless they explicitly say "open it anyway" — closed issues usually mean the work was already done or rejected.
Pick the branch prefix from labels.
- If any label name (case-insensitive) contains bug, fix, or defect → prefix is bug
- Otherwise → prefix is feature
- If the labels list is empty, default to feature and mention this in the final report so the user can correct it if needed.
Build the slug from the title.
- Lowercase
- Replace any run of non-alphanumeric chars with a single -
- Trim leading/trailing -
- Truncate to 40 characters max, then trim trailing - again
- Example: "Fix: edges disappear when deleting branched node" → fix-edges-disappear-when-deleting-branche
The branch name is then <prefix>/<num>-<slug>. Example: bug/207-fix-edges-disappear-when-deleting-branche.
Sync <BASE_BRANCH> and create the branch. Run sequentially:
```
git fetch origin <BASE_BRANCH>
git checkout -b <branch-name> origin/<BASE_BRANCH>
```
If the branch already exists locally:
- If we're already on it, just git pull --ff-only origin <BASE_BRANCH> (best-effort, may fail if there are commits — that's fine, just report) and skip to step 7.
- Otherwise ask the user whether to switch to it (git checkout <branch-name>) or abort. Do NOT delete or force-recreate the branch on your own.

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

2mo ago First seen · 64 lines · 0 tokens per session scan A 4c88e8c05148

Subscribe to this mod's changes

issue is a command published in the GitHub repository andrei-isvoran96/claude-skill-lab (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 792 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-31.

Git and workflow Project management

issue next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
issueandrei-isvoran96/claude-skill-lab	Command	1	5mo ago	MIT	A	0	Claude Code
merge-conflict-analysisrjmurillo/ai-agents	Command	49	today	MIT	A	0	GitHub Copilot
release-notesOpenHands/extensions	Command	178	yesterday	MIT	A	44	Claude Code
repo-audittractorjuice/arc-kit	Command	2.3k	today	none	A	29	Claude Code
commitechoVic/blade-code	Command	181	26d ago	MIT	A	8	Claude Code
propsmill/infrahub-mcp	Command	10	yesterday	Apache-2.0	A	18	Claude Code
codex-reviewoalders/kitchen-sink	Command	5	5d ago	MIT	A	41	Claude Code