scopes: Command for Claude Code

.claude/commands/pm/issue-status.md

issue-status is a command for Claude Code from kamiazya/scopes. It costs 0 tokens per session (499 once invoked), scanned A, original, Apache-2.0.

A command that reports the current state of a GitHub issue, an online task or bug record, along with related local progress.

In plain words
What is it for?
Use it to check whether an issue is open or closed, who owns it, when it changed, its labels, epic progress, and local synchronisation status.
Why use it?
It gathers issue details and local files in one report so developers can see ownership, labels, progress, and whether the two records match.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is kamiazya/scopes's own configuration. It tells Claude Code how to work on scopes 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 scopes configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kamiazya/scopes. 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/kamiazya/scopes/main/.claude/commands/pm/issue-status.md
Clone the repo
git clone --depth 1 https://github.com/kamiazya/scopes

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 issue-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/kamiazya/scopes/issue-status/github.svg)](https://agentmods.dev/commands/kamiazya/scopes/issue-status)
Your own site
<a href="https://agentmods.dev/commands/kamiazya/scopes/issue-status"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/issue-status/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 issue-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/kamiazya/scopes/issue-status"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/issue-status.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 499 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00499
Opus 5.5 $0.00000 $0.00200
Sonnet 5.5 $0.00000 $0.00100
Haiku 4.5 $0.00000 $0.00050

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

Security

Grade A, and why

issue-status 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.

.claude/commands/pm/issue-status.md · 79 lines

What it actually says

Issue Status

Check issue status (open/closed) and current state.

Usage

/pm:issue-status <issue_number>

Instructions

You are checking the current status of a GitHub issue and providing a quick status report for: Issue #$ARGUMENTS

1. Fetch Issue Status

Use GitHub CLI to get current status:

gh issue view #$ARGUMENTS --json state,title,labels,assignees,updatedAt

2. Status Display

Show concise status information:

🎫 Issue #$ARGUMENTS: {Title}
   
📊 Status: {OPEN/CLOSED}
   Last update: {timestamp}
   Assignee: {assignee or "Unassigned"}
   
🏷️ Labels: {label1}, {label2}, {label3}

3. Epic Context

If issue is part of an epic:

📚 Epic Context:
   Epic: {epic_name}
   Epic progress: {completed_tasks}/{total_tasks} tasks complete
   This task: {task_position} of {total_tasks}

4. Local Sync Status

Check if local files are in sync:

💾 Local Sync:
   Local file: {exists/missing}
   Last local update: {timestamp}
   Sync status: {in_sync/needs_sync/local_ahead/remote_ahead}

5. Quick Status Indicators

Use clear visual indicators:

  • 🟢 Open and ready
  • 🟡 Open with blockers
  • 🔴 Open and overdue
  • ✅ Closed and complete
  • ❌ Closed without completion

6. Actionable Next Steps

Based on status, suggest actions:

🚀 Suggested Actions:
   - Start work: /pm:issue-start $ARGUMENTS
   - Sync updates: /pm:issue-sync $ARGUMENTS
   - Close issue: gh issue close #$ARGUMENTS
   - Reopen issue: gh issue reopen #$ARGUMENTS

7. Batch Status

If checking multiple issues, support comma-separated list:

/pm:issue-status 123,124,125

Keep the output concise but informative, perfect for quick status checks during development of Issue #$ARGUMENTS.

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. 2mo ago First seen · 79 lines · 0 tokens per session scan A 542ad54e5634

Subscribe to this mod's changes

issue-status is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 11mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 499 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.

Related

issue-status compared with commands from other repositories

issue-status next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
issue-statuskamiazya/scopesCommand211mo agoApache-2.0A0Claude Code
diagnose-deeptracezscaler/zscaler-mcp-serverCommand5510d agoMITA29Claude Code
troubleshoot-experiencezscaler/zscaler-mcp-serverCommand5510d agoMITA25Claude Code
app-healthzscaler/zscaler-mcp-serverCommand5510d agoMITA16Claude Code
compare-locationszscaler/zscaler-mcp-serverCommand5510d agoMITA20Claude Code
investigate-alertszscaler/zscaler-mcp-serverCommand5510d agoMITA23Claude Code
investigate-sandboxzscaler/zscaler-mcp-serverCommand5510d agoMITA30Claude Code