start-issue-in-new-tab

start-issue-in-new-tab is a command for Claude Code from dapi/claude-code-marketplace. It costs 12 tokens per session (612 once invoked), scanned A, original, MIT.

A command that opens a new tab or pane in Zellij, a terminal workspace manager, and starts development for a GitHub issue there.

In plain words
What is it for?
Use it with an issue number, a number prefixed with #, or a full GitHub issue link.
Why use it?
It keeps work on a specific issue separate and starts the existing issue-development command in a dedicated terminal area.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument; mentions Claude Code.

Part of the zellij-workflow plugin — 1 skill, 2 commands shipped together

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.

agentmods
npx agentmods add commands/dapi/claude-code-marketplace/start-issue-in-new-tab
Clone the repo
git clone --depth 1 https://github.com/dapi/claude-code-marketplace

Made for: Claude Code.

Or install zellij-workflow, the plugin that ships this one along with the rest of its 1 skill, 2 commands.

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 start-issue-in-new-tab

README.md
[![agentmods](https://agentmods.dev/badge/commands/dapi/claude-code-marketplace/start-issue-in-new-tab.svg)](https://agentmods.dev/commands/dapi/claude-code-marketplace/start-issue-in-new-tab)
Your own site
<a href="https://agentmods.dev/commands/dapi/claude-code-marketplace/start-issue-in-new-tab"><img src="https://agentmods.dev/badge/commands/dapi/claude-code-marketplace/start-issue-in-new-tab.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00012 $0.00612
Opus 5 $0.00006 $0.00306
Sonnet 5 $0.00002 $0.00122
Haiku 4.5 $0.00001 $0.00061

Measured 6d ago against content hash d4169c08b22b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

start-issue-in-new-tab 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 6d 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.

zellij-workflow/commands/start-issue-in-new-tab.md · 87 lines

What it actually says

Start Issue in New Tab

Launch issue development in a new zellij tab or pane.

Input

  • ISSUE: $ARGUMENTS -- issue number, #number, or full GitHub URL

Steps

1. Parse issue number

parse_issue_number() {
  local arg="$1"

  # URL: https://github.com/.../issues/123
  if [[ "$arg" =~ github\.com/.*/issues/([0-9]+) ]]; then
    echo "${BASH_REMATCH[1]}"
  # #123 or 123
  elif [[ "$arg" =~ ^#?([0-9]+)$ ]]; then
    echo "${BASH_REMATCH[1]}"
  else
    echo ""
  fi
}

ISSUE_NUMBER=$(parse_issue_number "$ARGUMENTS")

2. Create tab and launch start-issue

In a new tab (default):

timeout 5 zellij action new-tab --name "#${ISSUE_NUMBER}" && \
sleep 0.3 && \
timeout 5 zellij action write-chars "start-issue $ISSUE_NUMBER
" || {
  _rc=$?
  echo "Command failed. Diagnosing..."
  if [ -z "$ZELLIJ" ]; then echo "Not in zellij session"
  elif [ $_rc -eq 124 ]; then echo "Timed out -- zellij may be hanging"
  elif ! command -v start-issue &>/dev/null; then echo "start-issue not found in PATH"
  else echo "Unknown error (exit code: $_rc)"
  fi
  exit $_rc
}

In a new pane:

timeout 5 zellij run -- start-issue $ISSUE_NUMBER || {
  _rc=$?
  echo "Command failed. Diagnosing..."
  if [ -z "$ZELLIJ" ]; then echo "Not in zellij session"
  elif [ $_rc -eq 124 ]; then echo "Timed out -- zellij may be hanging"
  elif ! command -v start-issue &>/dev/null; then echo "start-issue not found in PATH"
  else echo "Unknown error (exit code: $_rc)"
  fi
  exit $_rc
}

Examples

/start-issue-in-new-tab 123
/start-issue-in-new-tab #45
/start-issue-in-new-tab https://github.com/owner/repo/issues/78

Result

  • New zellij tab created with name #123
  • start-issue runs and:
    • Creates git worktree
    • Renames tab
    • Launches Claude Code session
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. 6d ago First seen · 87 lines · 12 tokens per session scan A d4169c08b22b

Subscribe to this mod's changes

start-issue-in-new-tab is a command published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 612 once invoked, about $0.0001 per session on Opus 5. 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-30.