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/analyze-and-create-issuegit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/analyze-and-create-issue)<a href="https://agentmods.dev/commands/sgaunet/claude-plugins/analyze-and-create-issue"><img src="https://agentmods.dev/badge/commands/sgaunet/claude-plugins/analyze-and-create-issue.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.00600 |
| Opus 5 | $0.00012 | $0.00300 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
analyze-and-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 5d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze And Create Issue Command
Analyze codebase to find improvements. For each improvement:
- Describe concisely to the user and ask if they want to create an issue
- If yes, create the issue in the git repository (GitHub, GitLab, or Forgejo) using the appropriate CLI.
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 issues are in the domain of
$argument. If no$argumentis provided, consider all types of issues. -
Get the list of labels for the current project:
- GitHub:
gh label list --repo <owner>/<repo> - GitLab:
glab label list - Forgejo:
fgj label list -R <owner>/<repo>
- GitHub:
-
For each improvement, Ask the user if they want to create an issue
-
If yes, Create Issue: Use the appropriate CLI:
- GitHub:
gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<label>" - GitLab:
glab issue create --title "<title>" --description "<body>" --label "<label>" - Forgejo:
fgj issue create -R <owner>/<repo> -t "<title>" -b "<body>" -l <label>
- GitHub:
Issue Content Guidelines
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 CLI is unavailable: Inform user to install
gh,glab, orfgjand suggest manual creation
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.
- 5d ago First seen · 54 lines · 23 tokens per session scan A 3a2e89e0051f
analyze-and-create-issue is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 600 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.
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.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.