maestro: Command for Claude Code

.claude/commands/triage-idea.md

triage-idea is a command for Claude Code from CarlosDanielDev/maestro. It costs 0 tokens per session (2,330 once invoked), scanned A, original, MIT.

A command for reviewing an idea recorded in a GitHub issue. It sends the issue to an idea-triage agent, checks the agent's structured report, and prints a summary without changing GitHub automatically.

In plain words
What is it for?
Use it with an issue number to assess an idea, validate the resulting report, and review a summary before approving any GitHub updates.
Why use it?
It turns an unreviewed idea into a checked report while requiring confirmation before comments or labels are changed.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions subagents.

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is PARSED_JSON=$(echo "$SUBAGENT_RESPONSE" | python3 .maestro/hooks/parse_idea_triager_report.py).

Reuse

Borrowing it

Nothing to install: this file belongs to CarlosDanielDev/maestro. 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/CarlosDanielDev/maestro/main/.claude/commands/triage-idea.md
Clone the repo
git clone --depth 1 https://github.com/CarlosDanielDev/maestro

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 triage-idea

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/carlosdanieldev/maestro/triage-idea"><img src="https://agentmods.dev/badge/commands/carlosdanieldev/maestro/triage-idea.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 2,330 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.02330
Opus 5.5 $0.00000 $0.00932
Sonnet 5.5 $0.00000 $0.00466
Haiku 4.5 $0.00000 $0.00233

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

Security

Grade A, and why

triage-idea 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 1mo 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/triage-idea.md · 240 lines

How it starts

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

Triage Idea

Run the upstream idea-inbox triage loop on a GitHub issue created from .github/ISSUE_TEMPLATE/idea.yml. Dispatches subagent-idea-triager, validates the structured report through .maestro/hooks/parse_idea_triager_report.py, and prints a digest. Does not mutate GitHub state without explicit user confirmation — every comment posting and label change is gated on a yes/no prompt. v0.16.1 is the foundation milestone; auto-mutation flows ship later (see Consultive Boundaries below).

Usage: /triage-idea #123 or /triage-idea 123


Arguments

$ARGUMENTS contains the idea issue number with an optional # prefix. Extract the first \d+ and reject if no number is present.


Instructions

Step 0: Parse arguments

Extract the first run of digits from $ARGUMENTS and re-validate the result is digits-only before exporting. Never pass $ARGUMENTS directly to gh.

IDEA_NUMBER=$(printf '%s' "$ARGUMENTS" | grep -oE '[0-9]+' | head -n1)
[[ "$IDEA_NUMBER" =~ ^[0-9]+$ ]] || {
  echo "no issue number in arguments" >&2
  exit 1
}
export IDEA_NUMBER

If no number is found, ask: "Which idea issue should I triage?" and stop.

Step 1: Confirm the issue exists and surface its labels

gh issue view "$IDEA_NUMBER" \
  --json number,title,labels,state,body \
  --jq '{number, title, state, labels: [.labels[].name], body}'
  • If gh is not installed or not authenticated → exit 1 with the standard hint (brew install gh / gh auth login).
  • If the issue does not exist → exit 1.
  • If the issue is CLOSED → exit 1. Re-open or pick a different issue.
  • If the labels do not include idea, print a warning and ask the user whether to proceed anyway. Some users may file ideas without the template; the triager can still score the body.

Step 2: Dispatch subagent-idea-triager

Invoke subagent-idea-triager via the Agent tool. Pass:

  • The full issue JSON from Step 1 (including title and body).
  • The repo name: gh repo view --json nameWithOwner --jq .nameWithOwner.

Read the full file on GitHub · 240 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. 1mo ago First seen · 240 lines · 0 tokens per session scan A 8747cc561e61

Subscribe to this mod's changes

triage-idea is a command published in the GitHub repository CarlosDanielDev/maestro (31 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,330 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-10-02.

Related

triage-idea compared with commands from other repositories

triage-idea next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
triage-ideaCarlosDanielDev/maestroCommand3120d agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code
speckit.bug.fixgithub/spec-kitCommand148kyesterdayMITA12Claude Code