Borrowing it
Nothing to install: this file belongs to nimble-giant/ailloy. 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/nimble-giant/ailloy/main/.claude/commands/create-issue.mdgit clone --depth 1 https://github.com/nimble-giant/ailloyWrote 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/nimble-giant/ailloy/create-issue)<a href="https://agentmods.dev/commands/nimble-giant/ailloy/create-issue"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/create-issue/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.
<a href="https://agentmods.dev/commands/nimble-giant/ailloy/create-issue"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/create-issue.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02558 |
| Opus 5.5 | $0.00000 | $0.01023 |
| Sonnet 5.5 | $0.00000 | $0.00512 |
| Haiku 4.5 | $0.00000 | $0.00256 |
Grade A, and why
create-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 2mo 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Github Issue
Purpose
This command is used to instruct Claude to generate GitHub issues with a clean, actionable, well-structured format. It is optimized for creating consistent GitHub issues for engineering planning, with consistent formatting across feat, fix, chore, docs, and epic types.
Command Name
create-issue
Invocation Syntax
You can invoke this command with optional flags:
/create-github-issue [flags] <description>
Flags
-b, --board <name>: Specify project board (default: "{{default_board}}")-l, --label <label>: Add labels to the issue (can be used multiple times)--prompt: Enable interactive mode (prompts for board and labels if supported)
Examples
# Basic issue creation (no board or labels)
/create-github-issue feat(web): add control family status card
# With project board
/create-github-issue --board "Tech Debt" fix(api): memory leak in cache
# With labels
/create-github-issue -l bug -l priority:high fix(security): patch vulnerability
# Multiple labels and board
/create-github-issue -b "Backend" -l enhancement -l good-first-issue feat(api): add new endpoint
# Interactive mode for teams with complex configurations
/create-github-issue --prompt feat(web): new feature requiring custom setup
Claude must:
- Immediately enter plan mode when this command is invoked
- Parse the user input to extract flags and issue description
- Format the GitHub issue using the exact markdown structure below
- Use the ExitPlanMode tool to present the formatted issue as the plan
- Wait for user approval before proceeding
- After approval:
- If
--promptflag is present: Use interactive mode (ask for board and labels if repository supports them) - Otherwise: Use parsed flags only (no prompting, no automatic assignments)
- If
- Execute the GitHub CLI commands to create the issue with configured settings
Plan Mode Output Format
In plan mode, Claude must present the issue using this exact structure:
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.
- 2mo ago First seen · 330 lines · 0 tokens per session scan A 90a7de578418
create-issue is a command published in the GitHub repository nimble-giant/ailloy (10 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,558 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
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.