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.
npx agentmods add commands/sgaunet/claude-plugins/create-issuegit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat 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 | $0.00017 | $0.00647 |
| Opus 5 | $0.00009 | $0.00324 |
| Sonnet 5 | $0.00003 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
create-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 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Issue Command
Create an issue for the current git repository. This command automatically detects whether the repository is hosted on GitHub, GitLab, or Forgejo and uses the appropriate CLI tool (gh, glab, or fgj).
Process
-
Detect Repository Host: Use the
detect-repo-hostskill to identify the hosting service (GitHub, GitLab, or Forgejo) and extract owner/repo details. -
Validate Arguments: Ensure the issue topic/description is provided as
$argument -
Always list available labels before creating the issue. Do not add labels that do not exist in the host repository.
- GitHub: Use
gh label list --repo <owner>/<repo>via Bash - GitLab: Use
glab label list - Forgejo: Use
fgj label list -R <owner>/<repo>
- GitHub: Use
-
Create Issue: Use the appropriate CLI tool:
- GitHub: Use
gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<label1>" --label "<label2>" - GitLab: Use
glab issue create --title "<title>" --description "<body>" --label "<label1>" --label "<label2>" - Forgejo: Use
fgj issue create -R <owner>/<repo> -t "<title>" -b "<body>" -l <label1> -l <label2>
- GitHub: Use
-
Request Permission: Always ask the user for permission before creating the issue
Issue Content Guidelines
The issue content should be based on: $argument
Requirements:
- Title: Clear, concise summary (max 80 characters)
- Description: Detailed explanation including:
- Problem description or feature request
- Steps to reproduce (if bug)
- Expected behavior
- Current behavior
- Additional context or screenshots
- Labels: Suggest appropriate labels based on those available in the host repository.
Formatting:
- Use proper markdown formatting
- Include code blocks with syntax highlighting when relevant
- Add checklists for actionable items
- Reference related issues or PRs when applicable
Error Handling
- If repository host detection fails: The
detect-repo-hostskill provides detailed error messages (not a git repo, no remotes, unsupported host) - If
gh/glab/fgjCLI not installed: Inform user and suggest installing the appropriate CLI tool
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.
- 2d ago First seen · 62 lines · 17 tokens per session scan A 55ab3dfedcb1
create-issue is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 647 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-30.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.