issue

A command for managing GitHub Issues, which are tracked tasks, bugs, or requests, from the maestro command line.

In plain words
What is it for?
Use it to list, create, assign, label, close, filter, or open GitHub Issues in a web browser.
Why use it?
It keeps common issue work alongside Git worktree and coding tasks instead of requiring separate browser steps.

Command

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/mirinodev/maestro/issue
Clone the repo
git clone --depth 1 https://github.com/mirinodev/maestro
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 942 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 $0.00000 $0.00942
Opus 5 $0.00000 $0.00471
Sonnet 5 $0.00000 $0.00188
Haiku 4.5 $0.00000 $0.00094

Measured 2d ago against content hash e2cfff12eca7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

docs/commands/issue.md · 186 lines

How it starts

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

🔸 issue

Command to manage GitHub Issues directly from maestro. Provides seamless integration between Git worktrees and GitHub issue management workflows.

Overview

mst issue [issue-number] [options]
mst issue [command] [options]

Arguments:

  • issue-number - Issue number to view or interact with
  • command - Special commands like list (equivalent to --list)

Usage Examples

Basic Usage

# List open issues
mst issue --list
mst issue list     # Alternative syntax

# Create new issue
mst issue --create

# Close specific issue
mst issue --close 123

# Open issue in web browser
mst issue 456 --web

Advanced Usage

# Create issue with assignment and labels
mst issue --create --assign @me --label bug,priority:high

# List issues with specific milestone
mst issue --list --milestone "v2.0"

# Interactive issue management
mst issue

Options

Option Short Description Default
--list -l List open issues false
--create -c Create new issue false
--close Close issue by number none
--web -w Open issue in web browser false
--assign <user> -a Assign issue to user none
--label <labels> Add labels (comma-separated) none
--milestone <name> Set milestone none

Note: You can use mst issue list as an alternative to mst issue --list.

Issue Management

Listing Issues

# List all open issues
mst issue --list
mst issue list     # Alternative syntax

# Filter by labels
mst issue --list --label bug

# Filter by assignee
mst issue --list --assign @me

Creating Issues

# Interactive creation
mst issue --create

# With metadata
mst issue --create --assign @teamlead --label enhancement

Closing Issues

# Close specific issue
mst issue --close 123

# Close with message
mst issue --close 123 --message "Fixed in latest commit"

Integration with Worktrees

Read the full file on GitHub · 186 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. 2d ago First seen · 186 lines · 0 tokens per session scan A e2cfff12eca7

Subscribe to this mod's changes

issue is a command published in the GitHub repository mirinodev/maestro (9 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 942 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.