issue-management

issue-management is a skill for Claude Code, Codex from saidsef/mcp-github-pr-issue-analyser. It costs 27 tokens per session (3,696 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.

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.

agentmods
npx agentmods add skills/saidsef/mcp-github-pr-issue-analyser/issue-management
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.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.svg" alt="Measured on agentmods" 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 3,696 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.03696
Opus 5 $0.00014 $0.01848
Sonnet 5 $0.00005 $0.00739
Haiku 4.5 $0.00003 $0.00370

Measured 6d ago against content hash 67cca6e0a734, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 · 304 lines

How it starts

The opening of the file, as written. The whole thing — 304 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 list_open_issues_prs with issue="issue" and filtering="repo" to check for a duplicate, or search_issues_prs to include closed ones
  2. Call list_repo_labels to see the label names the repository defines
  3. Call create_issue with a title, body and labels, plus a milestone title if it belongs to one
  4. The mcp label is appended automatically, so do not pass it yourself

Reading an Issue

  1. Call get_issue when you have the number and need the body, labels, assignees or milestone
  2. Read it back this way after create_issue, update_issue or update_assignees to confirm what landed

Updating an Issue

  1. Call 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 list_open_issues_prs, choosing filtering for the scope you want

Finding an Issue or PR

  1. Call 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 list_repo_labels for the repository
  2. Page through with page if the repository defines more than per_page labels

Running a Milestone

  1. Call list_milestones to see what the repository already tracks
  2. Call create_milestone for a new one, with a due date if the work has a deadline
  3. Pass milestone to create_issue to file an issue as it is opened
  4. Call set_issue_milestone to file or unfile an issue that already exists
  5. Call update_milestone with state="closed" once the work has shipped

Read the full file on GitHub · 304 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 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 4d ago), licensed Apache-2.0. It adds 27 tokens to every session and 3,696 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-31.