agentmods.dev

issue-management

issue-management is a skill for Claude Code, Codex from saidsef/mcp-github-pr-issue-analyser. It costs 27 tokens per session (4,607 once invoked), scanned A, original, Apache-2.0.

A GitHub issue and pull-request management workflow. Issues are tracked work items, while pull requests are proposed code changes awaiting review or merging.

In plain words
What is it for?
Use it to create, search, list, read, and update issues and pull requests, manage labels and assignees, and run milestones.
Why use it?
It helps keep repository work organised by checking duplicates, applying the right labels, updating only changed fields, and confirming changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 6repo changed 6d ago A scan SkillSpector: pass 27 tokens original Apache-2.0

Good fit Use it to create, search, list, read, and update issues and pull requests, manage labels and assignees, and run milestones.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/saidsef/mcp-github-pr-issue-analyser/issue-management
View source ↗ saidsef/mcp-github-pr-issue-analyser
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 saidsef/mcp-github-pr-issue-analyser --skill issue-management
Clone the repo
git clone --depth 1 https://github.com/saidsef/mcp-github-pr-issue-analyser

Made for: Claude Code, Codex.

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 issue-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/issue-management/github.svg)](https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/issue-management)
Your own site
<a href="https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/issue-management"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/issue-management/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 issue-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/issue-management"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/issue-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,607 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00027 $0.04607
Opus 5.5 $0.00011 $0.01843
Sonnet 5.5 $0.00005 $0.00921
Haiku 4.5 $0.00003 $0.00461

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

Security

Grade A, and why

issue-management 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 6d 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.

src/mcp_github/skills/issue-management/SKILL.md · 357 lines

How it starts

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

Issue Management

Create issues, update existing ones, list the open issues or PRs in a repo, org or user account, search for the ones you cannot already name, and read the labels a repository defines.

Prerequisites

  • repo_owner and repo_name for the target repository
  • GitHub token with repo write access

Workflow

Creating an Issue

  1. Call github_list_open_issues_prs with issue="issue" and filtering="repo" to check for a duplicate, or github_search_issues_prs to include closed ones
  2. Call github_list_repo_labels to see the label names the repository defines
  3. Write the title to the Title Convention and the body to the Issue Body template below
  4. Call github_create_issue with that title, body and labels, plus a milestone title if it belongs to one
  5. Call github_set_assignees with whoever owns the work
  6. The tool appends the mcp label to any labels you pass, so leave it out of the list. Omitting labels leaves the issue unlabelled

Reading an Issue

  1. Call github_get_issue when you have the number and need the body, labels, assignees or milestone
  2. Read it back this way after github_create_issue, github_update_issue or github_set_assignees to confirm what landed. github_set_assignees takes an issue_number and a list of logins, and the pr-management skill carries its parameters

Updating an Issue

  1. Call github_update_issue with only the fields you are changing, the rest keep their current values
  2. Pass state="closed" on its own to close a resolved issue

Listing Issues and PRs

  1. Call github_list_open_issues_prs, choosing filtering for the scope you want

Finding an Issue or PR

  1. Call github_search_issues_prs when you cannot already name the item, or need something closed
  2. Narrow with qualifiers in the query itself, e.g. repo:owner/name is:issue label:bug

Listing Labels

  1. Call github_list_repo_labels for the repository
  2. Page through with page if the repository defines more than per_page labels

Read the full file on GitHub · 357 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. 6d ago Changed 5e0f680bd720
  2. 11d ago Changed · +2 lines 4fcde65af745
  3. 22d ago Changed · +2 lines 94c3a11dd814
  4. 29d ago Changed · +2 lines 630b8125b73b
  5. 1mo ago Changed · +47 lines c6a089478737
  6. 1mo ago Changed 2cbf8d22c394
  7. 1mo ago First seen · 304 lines · 27 tokens per session scan A 67cca6e0a734

Subscribe to this mod's changes

issue-management is a skill published in the GitHub repository saidsef/mcp-github-pr-issue-analyser (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 4,607 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-08-31.

Git and workflowProject managementgithubmcpmcp-clientmcp-githubmcp-servermcp-tools
Related

Other skills, from other repositories

jira-release

Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.

decocms/studio · 60 tokens

release

MUST READ before preparing a release commit or GitHub release -- the blocking GitHub preflight (dev/releasepreflight.py), project.save() versioning, changelog, README, template sync verification, fresh-install smoke, and the post-push GitHub release procedure (references/github-release.md).

dylanroscover/Embody · 63 tokens

github-tool

GitHub integration tool. Fetches and creates issues and PRs via the gh CLI. Use when: Use when: you need to create or list issues and PRs, perform repository operations, or check tasks on GitHub.

xuiltul/animaworks · 49 tokens

github-ops

GitHub repository operations — issues, PRs, code search, and config-as-code workflows. Use when creating a GitHub issue for a network finding, opening a pull request for a config change, searching repos for IP or VLAN references, or committing an audit report to a repository.

automateyournetwork/netclaw · 61 tokens

jira-execute

Implement a Jira issue, open a pull request, and report the work on the issue. Insert into the prompt of a Jira column rule that does the building.

decocms/studio · 36 tokens

jira-merge

Land the pull requests a set of Jira issues carry, in order, resolving a conflict when one appears, and move each card on. Insert into the prompt of a run started on a batch of issues, or of a Jira column rule that ships.

decocms/studio · 54 tokens