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/create-issues.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/create-issues)<a href="https://agentmods.dev/commands/ibm-granite/granite.build/create-issues"><img src="https://agentmods.dev/badge/commands/ibm-granite/granite.build/create-issues.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.00025 | $0.01125 |
| Opus 5 | $0.00013 | $0.00562 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
create-issues 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Implementation Issues from Architecture Document
You are helping a developer turn an architecture/design document into a structured set of GitHub issues. The issues are created in the fork repo (derived from origin remote).
Architecture document path: $ARGUMENTS
Step 0: Validate input
If $ARGUMENTS is empty or the file does not exist, ask the user to provide a valid path:
Usage: /create-issues <path-to-architecture-document>
Example: /create-issues docs/plans/2026-02-23-architecture.md
Do not proceed until a valid path is provided.
Step 1: Read and analyze the document
- Read the architecture document at the given path
- Identify the top-level structure:
- Document title and overall goal
- Milestones (major sections, typically
## Milestone N: ...) - Sub-steps within each milestone (typically
### N.M ...) - Verification/acceptance criteria per milestone
- Files to create or modify per milestone
- 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|.*[:/][^/]+/(.*)(.git)?$|\1|' | sed 's/\.git$//')
Step 2: Decide granularity and propose issue plan
For each milestone, decide whether sub-steps should be individual issues or grouped:
- Split into separate issues when sub-steps are independent, touch different files, and are substantial enough to be a standalone PR
- Group into one issue when sub-steps are tightly coupled, touch the same files, or are small enough to implement together
Present the proposed issue hierarchy to the user:
Epic: <document title>
Milestone 1: <title>
- Issue: <description>
- Issue: <description>
Milestone 2: <title>
- Issue: <description>
...
Ask the user to approve or adjust the plan before creating any issues. Use AskUserQuestion.
Step 3: Create issues bottom-up
Create issues in this order so parent issues can reference child issue numbers:
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 · 160 lines · 25 tokens per session scan A 6806bdc9768b
create-issues is a command published in the GitHub repository ibm-granite/granite.build (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,125 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-09-04.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.