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 skills/saidsef/mcp-github-pr-issue-analyser/issue-managementnpx skills add saidsef/mcp-github-pr-issue-analyser --skill issue-managementgit clone --depth 1 https://github.com/saidsef/mcp-github-pr-issue-analyserWrote 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/skills/saidsef/mcp-github-pr-issue-analyser/issue-management)<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>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.1 | $0.00027 | $0.03696 |
| Opus 5 | $0.00014 | $0.01848 |
| Sonnet 5 | $0.00005 | $0.00739 |
| Haiku 4.5 | $0.00003 | $0.00370 |
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.
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_ownerandrepo_namefor the target repository- GitHub token with
repowrite access
Workflow
Creating an Issue
- Call
list_open_issues_prswithissue="issue"andfiltering="repo"to check for a duplicate, orsearch_issues_prsto include closed ones - Call
list_repo_labelsto see the label names the repository defines - Call
create_issuewith a title, body and labels, plus amilestonetitle if it belongs to one - The
mcplabel is appended automatically, so do not pass it yourself
Reading an Issue
- Call
get_issuewhen you have the number and need the body, labels, assignees or milestone - Read it back this way after
create_issue,update_issueorupdate_assigneesto confirm what landed
Updating an Issue
- Call
update_issuewith only the fields you are changing, the rest keep their current values - Pass
state="closed"on its own to close a resolved issue
Listing Issues and PRs
- Call
list_open_issues_prs, choosingfilteringfor the scope you want
Finding an Issue or PR
- Call
search_issues_prswhen you cannot already name the item, or need something closed - Narrow with qualifiers in the query itself, e.g.
repo:owner/name is:issue label:bug
Listing Labels
- Call
list_repo_labelsfor the repository - Page through with
pageif the repository defines more thanper_pagelabels
Running a Milestone
- Call
list_milestonesto see what the repository already tracks - Call
create_milestonefor a new one, with a due date if the work has a deadline - Pass
milestonetocreate_issueto file an issue as it is opened - Call
set_issue_milestoneto file or unfile an issue that already exists - Call
update_milestonewithstate="closed"once the work has shipped
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.
- 6d ago First seen · 304 lines · 27 tokens per session scan A 67cca6e0a734
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.
Other skills, from other repositories
github-tool
GitHub integration tool for listing and creating issues and PRs via the gh CLI wrapper. Use when: creating or listing issues or pull requests, or checking repository work on GitHub.
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.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
status
Show a comprehensive project status dashboard: task queue, blocked items, session state, verification, and git status.
issue-comment
Handle a non-build maintainer comment on an issue or PR — close, reopen, label, dedupe, answer a brief question, or triage. Action-only; redirect anything that needs code changes to /build.