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.
curl -O https://raw.githubusercontent.com/kamiazya/scopes/main/.claude/commands/pm/issue-start.mdgit clone --depth 1 https://github.com/kamiazya/scopesWrote 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.
[](https://agentmods.dev/commands/kamiazya/scopes/issue-start)<a href="https://agentmods.dev/commands/kamiazya/scopes/issue-start"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/issue-start/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.
<a href="https://agentmods.dev/commands/kamiazya/scopes/issue-start"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/issue-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01127 |
| Opus 5.5 | $0.00000 | $0.00451 |
| Sonnet 5.5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
issue-start 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Start
Begin work on a GitHub issue with parallel agents based on work stream analysis.
Usage
/pm:issue-start <issue_number>
Quick Check
-
Get issue details:
gh issue view $ARGUMENTS --json state,title,labels,bodyIf it fails: "❌ Cannot access issue #$ARGUMENTS. Check number or run: gh auth login"
-
Find local task file:
- First check if
.claude/epics/*/$ARGUMENTS.mdexists (new naming) - If not found, search for file containing
github:.*issues/$ARGUMENTSin frontmatter (old naming) - If not found: "❌ No local task for issue #$ARGUMENTS. This issue may have been created outside the PM system."
- First check if
-
Check for analysis:
test -f .claude/epics/*/$ARGUMENTS-analysis.md || echo "❌ No analysis found for issue #$ARGUMENTS Run: /pm:issue-analyze $ARGUMENTS first Or: /pm:issue-start $ARGUMENTS --analyze to do both"If no analysis exists and no --analyze flag, stop execution.
Instructions
1. Ensure Worktree Exists
Check if epic worktree exists:
# Find epic name from task file
epic_name={extracted_from_path}
# Check worktree
if ! git worktree list | grep -q "epic-$epic_name"; then
echo "❌ No worktree for epic. Run: /pm:epic-start $epic_name"
exit 1
fi
2. Read Analysis
Read .claude/epics/{epic_name}/$ARGUMENTS-analysis.md:
- Parse parallel streams
- Identify which can start immediately
- Note dependencies between streams
3. Setup Progress Tracking
Get current datetime: date -u +"%Y-%m-%dT%H:%M:%SZ"
Create workspace structure:
mkdir -p .claude/epics/{epic_name}/updates/$ARGUMENTS
Update task file frontmatter updated field with current datetime.
4. Launch Parallel Agents
For each stream that can start immediately:
Create .claude/epics/{epic_name}/updates/$ARGUMENTS/stream-{X}.md:
---
issue: $ARGUMENTS
stream: {stream_name}
agent: {agent_type}
started: {current_datetime}
status: in_progress
---
# Stream {X}: {stream_name}
## Scope
{stream_description}
## Files
{file_patterns}
## Progress
- Starting implementation
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 · 164 lines · 0 tokens per session scan A a92c0aaabd66
issue-start 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 1,127 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.
issue-start compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| issue-startkamiazya/scopes | Command | 2 | 11mo ago | Apache-2.0 | A | 0 | Claude Code |
| CHANGELOGbytedance/UI-TARS-desktop | Command | 40k | 29d ago | Apache-2.0 | A | 0 | Claude Code |
| diagnose-deeptracezscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 29 | Claude Code |
| create-access-rulezscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 20 | Claude Code |
| investigate-incidentzscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 27 | Claude Code |
| review-attack-surfacezscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 27 | Claude Code |
| create-timeout-rulezscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 21 | Claude Code |