What is create-github-issue?

A guided command for creating GitHub issues, which are tracked reports or requests in a software repository. It uses the repository's issue forms and submits the completed issue with GitHub CLI.

Use it to create structured bug reports and feature requests from the command line.

It helps collect the required details in the right format before filing a bug report or feature request.

How marcmodin/mcp-prompt-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to marcmodin/mcp-prompt-server. 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/marcmodin/mcp-prompt-server/main/.claude/commands/create-github-issue.md

Clone the repo

git clone --depth 1 https://github.com/marcmodin/mcp-prompt-server

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/marcmodin/mcp-prompt-server/create-github-issue/github.svg)](https://agentmods.dev/commands/marcmodin/mcp-prompt-server/create-github-issue)

Your own site

<a href="https://agentmods.dev/commands/marcmodin/mcp-prompt-server/create-github-issue"><img src="https://agentmods.dev/badge/commands/marcmodin/mcp-prompt-server/create-github-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/marcmodin/mcp-prompt-server/create-github-issue"><img src="https://agentmods.dev/badge/commands/marcmodin/mcp-prompt-server/create-github-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,673 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.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.01673
Opus 5.5	$0.00008	$0.00669
Sonnet 5.5	$0.00004	$0.00335
Haiku 4.5	$0.00002	$0.00167

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

Security

Grade A, and why

create-github-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.

.claude/commands/create-github-issue.md · 274 lines

How it starts

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

Create GitHub Issue

Context

You are a helpful assistant that guides users through creating well-structured GitHub issues. You follow the issue form templates defined in .github/ISSUE_TEMPLATE/ to gather all necessary information, then create and submit the issue using the GitHub CLI (gh command).

This project uses GitHub issue forms (YAML templates) for bug reports and feature requests.

Instructions

Follow this conversational workflow to create a GitHub issue:

1. Determine Issue Type

Ask the user what type of issue they want to create:

Bug Report: For reporting bugs and issues
Feature Request: For suggesting new features or enhancements

2. Read the Appropriate Template

Based on the issue type, read the corresponding template:

Bug Report: .github/ISSUE_TEMPLATE/bug_report.yml
Feature Request: .github/ISSUE_TEMPLATE/feature_request.yml

Parse the YAML template to understand required and optional fields.

3. Gather Information

Ask the user questions based on the template fields in a natural, conversational manner. For each field in the template's body:

input: Ask for text input
textarea: Ask for longer text responses
dropdown: Present options and ask user to choose
checkboxes: Present options for selection

Track which fields are required (validations.required: true) and ensure those are collected.

4. Detect Repository Information

Determine the GitHub repository:

First, try to detect from git remote: git remote get-url origin
If not available, ask the user for owner/repo

5. Format Issue Body

Construct the issue body by combining the gathered information according to the template structure. For each field, use the format:

### [Field Label]

[User's response]

6. Determine Labels

Based on issue type and template, apply appropriate labels:

Bug Report: bug, triage
Feature Request: feature, enhancement

Add priority-based labels if applicable: priority-low, priority-medium, priority-high, priority-critical

Read the full file on GitHub · 274 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.

2mo ago First seen · 274 lines · 21 tokens per session scan A 84eb62ecd14f

Subscribe to this mod's changes

create-github-issue is a command published in the GitHub repository marcmodin/mcp-prompt-server (1 stars, last pushed 1y ago), licensed MIT. It adds 21 tokens to every session and 1,673 once invoked, about $0.0001 per session on Opus 5.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-08-31.

Git and workflow Project management ai claude copilot mcp

create-github-issue next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
create-github-issuemarcmodin/mcp-prompt-server	Command	1	1y ago	MIT	A	21	Claude Code
speckit.git.commitgithub/spec-kit	Command	148k	yesterday	MIT	A	10	Claude Code
speckit.git.featuregithub/spec-kit	Command	148k	yesterday	MIT	A	9	Claude Code
speckit.git.validategithub/spec-kit	Command	148k	yesterday	MIT	A	8	Claude Code
speckit.git.remotegithub/spec-kit	Command	148k	yesterday	MIT	A	8	Claude Code
speckit.git.initializegithub/spec-kit	Command	148k	yesterday	MIT	A	8	Claude Code
merge-conflictspecstoryai/getspecstory	Command	1.4k	yesterday	Apache-2.0	A	4	Claude Code

mcp-prompt-server: Command for Claude Code