scopes: Command for Claude Code

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

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

A command that displays a GitHub issue together with its related sub-issues and local task files. A GitHub issue is a tracked piece of work, while sub-issues are smaller tasks connected to it.

In plain words
What is it for?
Use it to inspect an issue number, find its parent epic and related work, and see matching files under .claude/epics/.
Why use it?
It brings issue status, labels, ownership, dates, descriptions, dependencies, and local project-file links into one view. This avoids checking GitHub and the repository separately.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/kamiazya/scopes/issue-show"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/issue-show.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 621 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.00621
Opus 5.5 $0.00000 $0.00248
Sonnet 5.5 $0.00000 $0.00124
Haiku 4.5 $0.00000 $0.00062

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

Security

Grade A, and why

issue-show 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-show.md · 92 lines

How it starts

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

Issue Show

Display issue and sub-issues with detailed information.

Usage

/pm:issue-show <issue_number>

Instructions

You are displaying comprehensive information about a GitHub issue and related sub-issues for: Issue #$ARGUMENTS

1. Fetch Issue Data

  • Use gh issue view #$ARGUMENTS to get GitHub issue details
  • Look for local task file: first check .claude/epics/*/$ARGUMENTS.md (new naming)
  • If not found, search for file with github:.*issues/$ARGUMENTS in frontmatter (old naming)
  • Check for related issues and sub-tasks

2. Issue Overview

Display issue header:

🎫 Issue #$ARGUMENTS: {Issue Title}
   Status: {open/closed}
   Labels: {labels}
   Assignee: {assignee}
   Created: {creation_date}
   Updated: {last_update}
   
📝 Description:
{issue_description}

3. Local File Mapping

If local task file exists:

📁 Local Files:
   Task file: .claude/epics/{epic_name}/{task_file}
   Updates: .claude/epics/{epic_name}/updates/$ARGUMENTS/
   Last local update: {timestamp}

4. Sub-Issues and Dependencies

Show related issues:

🔗 Related Issues:
   Parent Epic: #{epic_issue_number}
   Dependencies: #{dep1}, #{dep2}
   Blocking: #{blocked1}, #{blocked2}
   Sub-tasks: #{sub1}, #{sub2}

5. Recent Activity

Display recent comments and updates:

💬 Recent Activity:
   {timestamp} - {author}: {comment_preview}
   {timestamp} - {author}: {comment_preview}
   
   View full thread: gh issue view #$ARGUMENTS --comments

6. Progress Tracking

If task file exists, show progress:

✅ Acceptance Criteria:
   ✅ Criterion 1 (completed)
   🔄 Criterion 2 (in progress)
   ⏸️ Criterion 3 (blocked)
   □ Criterion 4 (not started)

7. Quick Actions

🚀 Quick Actions:
   Start work: /pm:issue-start $ARGUMENTS
   Sync updates: /pm:issue-sync $ARGUMENTS
   Add comment: gh issue comment #$ARGUMENTS --body "your comment"
   View in browser: gh issue view #$ARGUMENTS --web

8. Error Handling

  • Handle invalid issue numbers gracefully
  • Check for network/authentication issues
  • Provide helpful error messages and alternatives

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

  1. 2mo ago First seen · 92 lines · 0 tokens per session scan A d33a1b6d053a

Subscribe to this mod's changes

issue-show 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 621 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-show compared with commands from other repositories

issue-show next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
issue-showkamiazya/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