Borrowing it
Nothing to install: this file belongs to opagani/cassini-workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opagani/cassini-workshop/main/.claude/commands/git-issue.mdgit clone --depth 1 https://github.com/opagani/cassini-workshopWrote 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.
[](https://agentmods.dev/commands/opagani/cassini-workshop/git-issue)<a href="https://agentmods.dev/commands/opagani/cassini-workshop/git-issue"><img src="https://agentmods.dev/badge/commands/opagani/cassini-workshop/git-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.
<a href="https://agentmods.dev/commands/opagani/cassini-workshop/git-issue"><img src="https://agentmods.dev/badge/commands/opagani/cassini-workshop/git-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00024 | $0.00450 |
| Opus 5.5 | $0.00010 | $0.00180 |
| Sonnet 5.5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
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 2mo 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.
This is a copy
100% identical to git-issue — 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.
What it actually says
issue
Create a GitHub issue using the github skill's template — direct,
detailed, no filler.
Behavior
- Preflight.
- Ensure
ghis installed and authenticated (gh auth status). - Confirm we're in a repo with a GitHub remote (
gh repo view).
- Ensure
- Gather context. If the user gave a short title or topic, expand it.
Read
docs/STORIES.md,docs/PLAN.md, ordocs/SPEC.mdif the topic maps to one of them — link the story or task id in the body. - Draft per the
githubskill 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.
- Title — Conventional-Commit style
(
feat(scope): …,fix(scope): …,chore: …). Lowercase, imperative, no period. - Show the user the draft title + body before creating. Confirm labels and assignee.
- Create with a HEREDOC body:
Addgh issue create --title "<title>" --body "$(cat <<'EOF' ... EOF )"--label,--assignee,--milestoneonly 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
ghisn't authenticated, stop and tell the user to rungh auth login.
Hand off
Report the issue URL returned by gh.
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.
- 2mo ago First seen · 50 lines · 24 tokens per session scan A 88b6a1e7f154
git-issue is a command published in the GitHub repository opagani/cassini-workshop (0 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 450 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git-issue, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
start-development
Start the available Software Development Flow in Moira.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
retro
Generate a timestamped arc retrospective from the past 7 days of git history in /.agentskills.
gsd:complete-milestone
Archive completed milestone and prepare for next version.
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd:pause-work
Create context handoff when pausing work mid-phase.