agentmods.dev

analyze-and-create-issue

analyze-and-create-issue is a skill for Claude Code from sgaunet/claude-plugins. It costs 23 tokens per session (606 once invoked), scanned A, original, MIT.

A codebase analysis workflow that finds possible improvements and, with your approval, creates issues in GitHub, GitLab, or Forgejo. These are services for hosting Git repositories and tracking work.

In plain words
What is it for?
Use it to inspect a repository, describe improvement opportunities, check available labels, and create a labeled issue for each approved finding.
Why use it?
It turns findings into trackable work without making issues automatically or requiring you to format them by hand.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the software-engineering plugin — 18 skills, 7 agents shipped together

not rated 16repo 8d ago A scan 23 tokens original MIT

Good fit Use it to inspect a repository, describe improvement opportunities, check available labels, and create a labeled issue for each approved finding.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sgaunet/claude-plugins/analyze-and-create-issue
View source ↗ sgaunet/claude-plugins
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 sgaunet/claude-plugins --skill analyze-and-create-issue
Clone the repo
git clone --depth 1 https://github.com/sgaunet/claude-plugins

Made for: Claude Code.

Or install software-engineering, the plugin that ships this one along with the rest of its 18 skills, 7 agents.

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.

agentmods badge for analyze-and-create-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/sgaunet/claude-plugins/analyze-and-create-issue/github.svg)](https://agentmods.dev/skills/sgaunet/claude-plugins/analyze-and-create-issue)
Your own site
<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/analyze-and-create-issue"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/analyze-and-create-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.

agentmods 80×15 button for analyze-and-create-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/analyze-and-create-issue"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/analyze-and-create-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 606 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00606
Opus 5.5 $0.00009 $0.00242
Sonnet 5.5 $0.00005 $0.00121
Haiku 4.5 $0.00002 $0.00061

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

Security

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 22d 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/software-engineering/skills/analyze-and-create-issue/SKILL.md · 55 lines

How it starts

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

Analyze And Create Issue

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

  1. Detect Repository Host: Use the detect-repo-host skill to identify the hosting service (GitHub, GitLab, or Forgejo) and extract owner/repo details.

  2. Validate Arguments: Ensure the issues are in the domain of $argument. If no $argument is provided, consider all types of issues.

  3. 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>

  4. For each improvement, Ask the user if they want to create an issue

  5. 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>

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-host skill provides detailed error messages (not a git repo, no remotes, unsupported host)
  • If CLI is unavailable: Inform user to install gh, glab, or fgj and suggest manual creation

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

  1. 22d ago First seen · 55 lines · 23 tokens per session scan A 60d612454a22

Subscribe to this mod's changes

analyze-and-create-issue is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 606 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-25.

Claude CodeDevOps and cloudGit and workflowProject managementai-agentsclaude-code-marketplaceclaude-code-pluginsdeveloper-tools
Related

Other skills, from other repositories

glab

Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.

NikiforovAll/claude-code-rules · 59 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

phuryn/pm-skills · 52 tokens

sprint-plan

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

phuryn/pm-skills · 42 tokens

review-resume

Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.

phuryn/pm-skills · 49 tokens

identify-assumptions-new

Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture.

phuryn/pm-skills · 50 tokens