create-github-issue

A guided way to open GitHub issues from the command line, using the repository’s own issue templates. GitHub issues are records for bugs, feature requests, and other work in a code repository.

In plain words
What is it for?
Use it to file bug reports, feature requests, and draft issues, including labels, assignees, and milestones.
Why use it?
It avoids guessing which fields or labels a repository requires. It also gathers relevant project context so the issue is complete and consistent.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/tailcallhq/forgecode/create-github-issue
Any agent
npx skills add tailcallhq/forgecode --skill create-github-issue
Clone the repo
git clone --depth 1 https://github.com/tailcallhq/forgecode

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 989 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00063 $0.00989
Opus 5 $0.00032 $0.00495
Sonnet 5 $0.00013 $0.00198
Haiku 4.5 $0.00006 $0.00099

Measured yesterday against content hash ca343317ef87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.forge/skills/create-github-issue/SKILL.md · 99 lines

How it starts

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

Create GitHub Issue

Create comprehensive GitHub issues using gh issue create by dynamically discovering and adhering to the repository's official issue templates.

Workflow

1. Discover and Select Template

CRITICAL: You must use the repository's official templates. Do not assume the structure.

  1. List available templates:
    ls .github/ISSUE_TEMPLATE/
    
  2. Select the most appropriate template based on the issue type (e.g., bug_report.yml, feature_request.yml).
  3. Read the selected template to understand its required fields, structure, and any title prefixes or default labels.
    cat .github/ISSUE_TEMPLATE/<selected_template>.yml
    

2. Gather Context

Gather relevant information to fulfill the template requirements:

# Check current git status for context
git status

# View recent commits if related to codebase changes
git log --oneline -10

# Check if related issues exist
gh issue list --search "keyword" --limit 10

3. Generate Markdown Body

MANDATORY: Structure the issue body exactly as defined in the selected YAML template without exception.

  1. Map YAML fields to Markdown: Convert each field in the template (typically found under body:) into a Markdown section.
  2. Use Headers: Use the label or id from the YAML field as an H2 header (e.g., ## Bug Description).
  3. Respect Validation: Ensure all fields marked as required: true in the YAML are populated with meaningful content.
  4. Format Correctly: Use code blocks (e.g., ```shell, ```yaml) for logs and configurations as suggested by the template's render attribute.

4. Choose Labels

Select labels by inspecting .github/labels.json.

  • Primary Label: Always include a type: label that matches the issue type.
  • Additional Labels: Add relevant state:, work:, or priority: labels if they exist in the configuration.
  • Constraint: Only use labels defined in .github/labels.json.

Read the full file on GitHub · 99 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. yesterday First seen · 99 lines · 63 tokens per session scan A ca343317ef87

Subscribe to this mod's changes

create-github-issue is a skill published in the GitHub repository tailcallhq/forgecode (7,599 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 989 once invoked, about $0.0003 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-08-30.