issue-create

issue-create is a skill for Claude Code from terrylica/cc-skills. It costs 43 tokens per session (3,466 once invoked), scanned A, original, MIT.

A GitHub issue-creation workflow that formats bug reports, feature requests, questions, and documentation tasks. It can detect the repository, suggest labels from its existing system, and connect related issues.

In plain words
What is it for?
Use it to file a bug, request a feature, ask a question, or create a documentation task with repository-specific formatting and labels.
Why use it?
It reduces inconsistent issue descriptions and the manual work of finding the right repository, labels, and related reports. It also helps avoid creating duplicate issues.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the gh-tools plugin — 6 skills shipped together , and of cc-skills

Good fit Use it to file a bug, request a feature, ask a question, or create a documentation task with repository-specific formatting and labels.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/terrylica/cc-skills/issue-create
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.

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

Made for: Claude Code.

Or install gh-tools, the plugin that ships this one along with the rest of its 6 skills.

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.

agentmods badge for issue-create

README.md
[![agentmods](https://agentmods.dev/badge/skills/terrylica/cc-skills/issue-create/github.svg)](https://agentmods.dev/skills/terrylica/cc-skills/issue-create)
Your own site
<a href="https://agentmods.dev/skills/terrylica/cc-skills/issue-create"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/issue-create/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.

agentmods 80×15 button for issue-create

Your own site · 80×15
<a href="https://agentmods.dev/skills/terrylica/cc-skills/issue-create"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/issue-create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,466 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 271
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Rogue Agent · line 358
    Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
    Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
How audits are shown
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.1 $0.00043 $0.03466
Opus 5.5 $0.00017 $0.01386
Sonnet 5.5 $0.00009 $0.00693
Haiku 4.5 $0.00004 $0.00347

Measured 20d ago against content hash ef695b6ce870, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue-create 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 20d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/gh-issue-image-upload.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/gh-tools/skills/issue-create/SKILL.md · 363 lines

How it starts

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

Issue Create Skill

Create well-formatted GitHub issues with intelligent automation including AI-powered label suggestions, content type detection, template formatting, and related issue linking.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

When to Use This Skill

Use this skill when:

  • Creating bug reports, feature requests, questions, or documentation issues
  • Need AI-powered label suggestions from repository's existing taxonomy
  • Want automatic duplicate detection and related issue linking
  • Need consistent issue formatting across different repositories

Invocation

Slash command: /gh-tools:issue-create

Natural language triggers:

  • "Create an issue about..."
  • "File a bug for..."
  • "Submit a feature request..."
  • "Report this problem to..."
  • "Post an issue on GitHub..."

Features

1. Repository Detection

  • Auto-detects repository from current git directory
  • Supports explicit --repo owner/repo flag
  • Checks permissions before attempting to create

2. Content Type Detection

  • AI-powered detection (gpt-4.1 via gh-models)
  • Fallback to keyword matching
  • Types: Bug, Feature, Question, Documentation

3. Title Extraction

  • Extracts informative title from content
  • Adds type prefix (Bug:, Feature:, etc.)
  • Maximizes GitHub's 256-character limit for informative titles

4. Body Limit Maximization (65,536 Characters)

GitHub issue bodies support 65,536 characters (not bytes — UTF-8 multibyte characters count as 1). Always aim to fill a single post rather than splitting across multiple issues or comments.

Principle: One comprehensive post is more valuable than many fragmented ones. Pack as much analysis, context, history, and multi-perspective reasoning as possible into a single issue body or comment.

When composing long-form issue content:

Read the full file on GitHub · 363 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 20d ago Changed · +2 lines ef695b6ce870
  2. 28d ago Changed · +15 tokens per session e04bfdbe1a85
  3. 1mo ago First seen · 361 lines · 28 tokens per session scan A 8097cb6eb553

Subscribe to this mod's changes

issue-create is a skill published in the GitHub repository terrylica/cc-skills (0 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 3,466 once invoked, about $0.0002 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-09-05.

Related

Other skills, from other repositories

nav-pilot

Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).

qf-studio/navigator · 62 tokens

github-project-management

GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.

frankxai/claude-skills-library · 49 tokens

wrap-up

End-of-session handler: checks if the plan is complete. If complete: quick retrospective, forward follow-up prompt, and (in a repo) refresh + clean gone branches. If incomplete: skip cleanup, emit resume prompts. Cleanup needs a repo; rest doesn't.

dryvist/claude-code-plugins · 56 tokens

afkkit

Run a groomed ready GitHub issue through the whole build span unattended, covering worktree, implement, commit, QA plan, acceptance check, fix, and open PR, so one issue reaches a reviewable PR with no human at the keyboard. Use when the user says "run issue #N unattended" or "work the ready issues while I'm away". It…

mimukit/skills · 92 tokens

issuekit

Own the GitHub issue lifecycle in five modes: create issues from a plan or description, start a ready or stacked issue into its own worktree, close one out once its PR merges, sync PR↔issue links and dependents after merge, and triage the tracker for lifecycle, priority, and title gaps. Use when the user says "create…

mimukit/skills · 137 tokens

orcakit

Keep the Orca desktop app's workspace list honest about the git worktrees your workflow actually creates: link each one to its issue, keep its status current, and clean out the ones whose work already merged. Use when the user says "orcakit", "clean up my orca workspaces", "my Orca sidebar is full of finished work"…

mimukit/skills · 110 tokens