github-issue-creator

A GitHub issue assistant that follows a repository's issue templates and labels when preparing an issue. GitHub issues are written records of bugs, requests, and other work.

In plain words
What is it for?
It is for creating bug reports, feature requests, and other GitHub issues through the repository's templates.
Why use it?
It removes the guesswork from choosing the right format, required fields, and label for an issue.

Skill for Claude CodeCodexGemini CLI

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/itallstartedwithaidea/gemini-cli-googleadsagent/github-issue-creator
Any agent
npx skills add itallstartedwithaidea/gemini-cli-googleadsagent --skill github-issue-creator
Clone the repo
git clone --depth 1 https://github.com/itallstartedwithaidea/gemini-cli-googleadsagent

Made for: Claude Code, Codex, Gemini CLI.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 698 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00038 $0.00698
Opus 5 $0.00019 $0.00349
Sonnet 5 $0.00008 $0.00140
Haiku 4.5 $0.00004 $0.00070

Measured 2d ago against content hash 298aa6043c40, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-issue-creator 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.

Origin

This is a copy

100% identical to github-issue-creator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.gemini/skills/github-issue-creator/SKILL.md · 77 lines

How it starts

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

GitHub Issue Creator

This skill guides the creation of high-quality GitHub issues that adhere to the repository's standards and use the appropriate templates.

Workflow

Follow these steps to create a GitHub issue:

  1. Identify Issue Type: Determine if the request is a bug report, feature request, or other category.

  2. Locate Template: Search for issue templates in .github/ISSUE_TEMPLATE/.

    • bug_report.yml
    • feature_request.yml
    • website_issue.yml
    • If no relevant YAML template is found, look for .md templates in the same directory.
  3. Read Template: Read the content of the identified template file to understand the required fields.

  4. Draft Content: Draft the issue title and body/fields.

    • If using a YAML template (form), prepare values for each id defined in the template.
    • If using a Markdown template, follow its structure exactly.
    • Default Label: Always include the 🔒 maintainer only label unless the user explicitly requests otherwise.
  5. Create Issue: Use the gh CLI to create the issue.

    • CRITICAL: To avoid shell escaping and formatting issues with multi-line Markdown or complex text, ALWAYS write the description/body to a temporary file first.

    For Markdown Templates or Simple Body:

    # 1. Write the drafted content to a temporary file
    # 2. Create the issue using the --body-file flag
    gh issue create --title "Succinct title" --body-file <temp_file_path> --label "🔒 maintainer only"
    # 3. Remove the temporary file
    rm <temp_file_path>
    

    For YAML Templates (Forms): While gh issue create supports --body-file, YAML forms usually expect key-value pairs via flags if you want to bypass the interactive prompt. However, the most reliable non-interactive way to ensure formatting is preserved for long text fields is to use the --body or --body-file if the form has been converted to a standard body, OR to use the --field flags for YAML forms.

Read the full file on GitHub · 77 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. 2d ago First seen · 77 lines · 38 tokens per session scan A 298aa6043c40

Subscribe to this mod's changes

github-issue-creator is a skill published in the GitHub repository itallstartedwithaidea/gemini-cli-googleadsagent (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 698 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to github-issue-creator, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

collaboration-intelligence

Maintain and use a cross-channel collaboration map of rooms, people, agents, agent owners, relationships, expertise, ownership, roster, priority/VIP handling, and recent context. Trigger when a task or message carries room/channel/sender/member metadata; the user asks who is in a room, what it is for, who owns or…

sonichi/sutando · 208 tokens

schedule-crons

Re-create all session cron jobs for Sutando. Run this on startup or after a session restart.

sonichi/sutando · 0 tokens

task-orphan-check

Resolve orphan tasks left in /tasks/ from a previous session that crashed mid-execution. Classifies each live task as done / fresh / stale by cross-referencing per-side-effect markers, then archives or recovers as appropriate. Runs once on startup; safe to re-invoke.

sonichi/sutando · 65 tokens

agent-room-ops

One skill, multiple tools. Everything an agent does in a room beyond its task inbox lives here as a tool, so the parity capabilities are self-evidently one collection (not N scattered skills). Each tool is a thin gateway-only client verb sharing gateway.py; the gateway/broker (box-side) owns the platform creds and…

sonichi/sutando · 0 tokens

engine-conflict-resolve

Ask Sutando to resolve a conflicted update of a Sutando checkout. When pulling the latest release/main conflicts with local changes, Sutando reproduces the merge in a scratch git worktree, resolves the conflicts there, proposes the resolution to the owner, and fast-forwards the live checkout only after explicit…

sonichi/sutando · 87 tokens

claude-codex

Bash wrapper around the local Codex CLI for non-interactive runs from inside Sutando (bridges, cron, scripts). For interactive code review or task hand-off from this Claude Code session, prefer the official /codex: plugin commands; this skill is the file-bridge-compatible path that discord-bridge.py invokes for…

sonichi/sutando · 81 tokens