What is github-issue?

A skill for opening a GitHub issue, bug report, feature request, or discussion. GitHub is a service where software projects host code and track work in issues and discussions.

It is for filing bugs, requesting features, or starting discussions in any GitHub repository.

It provides a defined workflow for creating these records, including when the project is not checked out on the user's computer.

github-issue — Skill for Claude Code by LandonSchropp/agent-toolkit

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 LandonSchropp/agent-toolkit --skill github-issue

Clone the repo

git clone --depth 1 https://github.com/LandonSchropp/agent-toolkit

Made for: Claude Code.

Or install ls-git, the plugin that ships this one along with the rest of its 9 skills, 1 hook.

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/skills/landonschropp/agent-toolkit/github-issue/github.svg)](https://agentmods.dev/skills/landonschropp/agent-toolkit/github-issue)

Your own site

<a href="https://agentmods.dev/skills/landonschropp/agent-toolkit/github-issue"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/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/skills/landonschropp/agent-toolkit/github-issue"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/github-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,260 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.00030	$0.01260
Opus 5.5	$0.00012	$0.00504
Sonnet 5.5	$0.00006	$0.00252
Haiku 4.5	$0.00003	$0.00126

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

Security

Grade A, and why

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 24d 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.

plugins/ls-git/skills/github-issue/SKILL.md · 82 lines

How it starts

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

GitHub Issue

Check It Isn't Already Handled

Search both, since a repository that routes features to discussions won't have them among its issues:

gh issue list --repo <owner>/<repo> --search "<terms>" --state all
gh discussion list --repo <owner>/<repo> --search "<terms>" --state all

Then confirm the thing being asked for doesn't already exist, which is a different question from whether it's been reported. Check the README, the changelog, and the tool's own --help.

Any hit ends the task. Tell the user what you found, with a link where there is one, and let them decide.

Follow The Repository's Template

Maintainers wrote the template so reports arrive in a shape they can triage, and inventing a structure instead is the fastest way to get an issue closed. Before writing anything, find out what the repository expects, using gh api repos/<owner>/<repo>/contents/<path> when there's no local checkout:

List .github/ISSUE_TEMPLATE/ for issue forms and Markdown templates, and check the legacy .github/ISSUE_TEMPLATE.md.
Read .github/ISSUE_TEMPLATE/config.yml. blank_issues_enabled: false means the maintainers expect one of the listed templates, and contact_links may route this kind of report somewhere else entirely.
Check whether the repository routes this kind of report to discussions instead. The deciding evidence is contact_links or CONTRIBUTING.md, not gh repo view <owner>/<repo> --json hasDiscussionsEnabled on its own, since plenty of repositories enable discussions and still take feature requests as issues. When they do route it, look for a matching form in .github/DISCUSSION_TEMPLATE/, draft a discussion, and say so when presenting it for review.
Read CONTRIBUTING.md.

Fill in every field the chosen template asks for, and delete nothing but its instructional comments. A Markdown template keeps its headings and their order. A YAML issue form has no headings of its own: each field's label becomes a ### <label> heading, in the file's order, and every required: true field must be answered. When several templates could fit, ask the user which one.

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

24d ago Changed · +3 lines 1d4062309026
29d ago Changed · +3 lines 8589dd253024
1mo ago First seen · 76 lines · 30 tokens per session scan A 9e5ce17512be

Subscribe to this mod's changes

github-issue is a skill published in the GitHub repository LandonSchropp/agent-toolkit (3 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,260 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-09-07.

Claude Code Git and workflow Project management agents codex-cli mcp skills

git-issue-create

Open one standalone GitHub issue with gh - duplicate-checked first, conventional title, repo-template-aware body, auto-resolved labels. Use for every issue-filing request however casual: "open an issue", "file a bug", "make a ticket", "/git-issue-create", "track this", "note this down", "we should fix X later", or…

pivoshenko/pivoshenko.ai · 157 tokens

git-issue-triage

Groom an open GitHub backlog with gh - one read-only sweep, every open issue bucketed into exactly one category (unlabeled, unprioritized, stale, likely duplicate, closeable, blocked, healthy), a per-issue report, per-category confirmation, then batched label / state / comment edits. Use when the user says "triage…

pivoshenko/pivoshenko.ai · 204 tokens

git-issue-start

Take a GitHub issue from open to a checked-out branch - assign it to you, mark it in progress if the repo has such a label, derive a conventional branch name from its type: label, branch off the detected base. Use for "start issue 42", "work on #42", "/git-issue-start 42", "let's do 42", "pick up that issue", "take…

pivoshenko/pivoshenko.ai · 174 tokens

github-issue