git-issue

A command for creating a detailed issue in GitHub, the service commonly used to track code, bugs, and planned work.

In plain words
What is it for?
Use it to prepare and open an issue after checking GitHub authentication, the repository, and relevant project documents.
Why use it?
It turns a short request into a structured issue with context, the desired change, and observable acceptance criteria.

Command for Claude Code

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 commands/robconery/cassini-workshop/git-issue
Clone the repo
git clone --depth 1 https://github.com/robconery/cassini-workshop

Made for: Claude Code.

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 450 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.00024 $0.00450
Opus 5 $0.00012 $0.00225
Sonnet 5 $0.00005 $0.00090
Haiku 4.5 $0.00002 $0.00045

Measured yesterday against content hash 88b6a1e7f154, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-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

2 near-identical copies found in the catalogue:

  • git-issue — 100% identical, 0 lines differ
  • git-issue — 100% identical, 0 lines differ
.claude/commands/git-issue.md · 50 lines

What it actually says

issue

Create a GitHub issue using the github skill's template — direct, detailed, no filler.

Behavior

  1. Preflight.
    • Ensure gh is installed and authenticated (gh auth status).
    • Confirm we're in a repo with a GitHub remote (gh repo view).
  2. Gather context. If the user gave a short title or topic, expand it. Read docs/STORIES.md, docs/PLAN.md, or docs/SPEC.md if the topic maps to one of them — link the story or task id in the body.
  3. Draft per the github skill issue template:
    • Context — where it came from, why it matters, links.
    • What we want — the concrete change or behavior.
    • Acceptance criteria — observable, checkbox list.
    • Notes — anything that helps the next person.
  4. Title — Conventional-Commit style (feat(scope): …, fix(scope): …, chore: …). Lowercase, imperative, no period.
  5. Show the user the draft title + body before creating. Confirm labels and assignee.
  6. Create with a HEREDOC body:
    gh issue create --title "<title>" --body "$(cat <<'EOF'
    ...
    EOF
    )"
    
    Add --label, --assignee, --milestone only when known.

Rules

  • Never invent acceptance criteria — pull them from the source story/spec or ask the user.
  • Never include secrets or paths to local-only files.
  • If gh isn't authenticated, stop and tell the user to run gh auth login.

Hand off

Report the issue URL returned by gh.

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 · 50 lines · 24 tokens per session scan A 88b6a1e7f154

Subscribe to this mod's changes

git-issue is a command published in the GitHub repository robconery/cassini-workshop (1 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 450 once invoked, about $0.0001 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-31.