Borrowing it
Nothing to install: this file belongs to ibm-granite/granite.build. 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/ibm-granite/granite.build/main/.claude/commands/start-issue.mdgit clone --depth 1 https://github.com/ibm-granite/granite.buildWrote 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/ibm-granite/granite.build/start-issue)<a href="https://agentmods.dev/commands/ibm-granite/granite.build/start-issue"><img src="https://agentmods.dev/badge/commands/ibm-granite/granite.build/start-issue.svg" alt="Measured on agentmods" 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.00019 | $0.01343 |
| Opus 5 | $0.00010 | $0.00672 |
| Sonnet 5 | $0.00004 | $0.00269 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade B, and why
start-issue scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cp -r .claude/settings.json $WORKTREE_BASE/<branch-name>/.claude/settings.json 2>/dev/null || true How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Work on a GitHub Issue
You are helping a developer start work on a GitHub issue. You will verify pre-conditions, create an isolated git worktree, load the issue and architecture documentation, assess what's already been implemented, and plan the work. Follow these steps in order, stopping if any step fails.
Issue number: $ARGUMENTS
Defaults
These values can be overridden by the user but apply by default:
ARCH_DOC_1=docs/plans/2026-02-23-architecture.md
ARCH_DOC_2=docs/plans/2026-02-18-standalone-deployment-design.md
WORKTREE_BASE=../granite.build-worktrees
Derive the fork owner and repo:
FORK_OWNER=$(git remote get-url origin | sed -E 's|.*[:/]([^/]+)/.*|\1|')
FORK_REPO=$(git remote get-url origin | sed -E 's|.*[:/][^/]+/(.*)$|\1|' | sed 's/\.git$//')
Step 0: Pre-flight checks
- If
$ARGUMENTSis empty or not a number, show usage and stop:Usage: /start-issue <issue-number> Example: /start-issue 42 - Confirm we are on the
mainbranch:
If not ongit branch --show-currentmain, warn the user and ask whether to switch (git checkout main) or abort. - Check for uncommitted changes:
If there are uncommitted changes, ask the user what to do:git status --porcelain- Commit them before proceeding (always use
git commit -s— the upstream repo enforces the DCO check) - Stash them (
git stash push -m "stash before issue-$ARGUMENTS") - Abort and let the user handle it manually
- Commit them before proceeding (always use
- Fetch the latest upstream:
git fetch upstream
Step 1: Create branch and worktree
-
Fetch the issue title to verify the issue exists and to derive the branch name:
gh issue view $ARGUMENTS --repo "$FORK_OWNER/$FORK_REPO" --json title --template '{{.title}}'If the command fails (issue doesn't exist), report the error and stop.
-
Slugify the title: lowercase, replace non-alphanumeric characters with hyphens, collapse consecutive hyphens, strip leading/trailing hyphens, truncate the slug so the total branch name (
issue-$ARGUMENTS-<slug>) stays under 50 characters. Branch name:issue-$ARGUMENTS-<slug>
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.
- 2d ago First seen · 130 lines · 19 tokens per session scan B 15fa591b8d20
start-issue is a command published in the GitHub repository ibm-granite/granite.build (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,343 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.