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 skills add devantler-tech/agent-plugins --skill github-issuesgit clone --depth 1 https://github.com/devantler-tech/agent-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/skills/devantler-tech/agent-plugins/github-issues)<a href="https://agentmods.dev/skills/devantler-tech/agent-plugins/github-issues"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/github-issues/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.
<a href="https://agentmods.dev/skills/devantler-tech/agent-plugins/github-issues"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/github-issues.svg" alt="Reviewed on agentmods" width="80" 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.00160 | $0.02310 |
| Opus 5.5 | $0.00064 | $0.00924 |
| Sonnet 5.5 | $0.00032 | $0.00462 |
| Haiku 4.5 | $0.00016 | $0.00231 |
Grade A, and why
github-issues 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 3d 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.
This is a copy
94% identical to github-issues — 33 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Manage GitHub issues using the @modelcontextprotocol/server-github MCP server.
Available Tools
MCP Tools (read operations)
| Tool | Purpose |
|---|---|
mcp__github__issue_read |
Read issue details, sub-issues, comments, labels (methods: get, get_comments, get_sub_issues, get_labels) |
mcp__github__list_issues |
List and filter repository issues by state, labels, date |
mcp__github__search_issues |
Search issues across repos using GitHub search syntax |
mcp__github__projects_list |
List projects, project fields, project items, status updates |
mcp__github__projects_get |
Get details of a project, field, item, or status update |
mcp__github__projects_write |
Add/update/delete project items, create status updates |
MCP Tools (write operations)
| Tool | Purpose |
|---|---|
mcp__github__issue_write |
Create or update an issue (methods: create, update). Supports title, body, type, labels, assignees, milestone, and issue fields |
mcp__github__add_issue_comment |
Add a comment or a reaction to an issue |
mcp__github__sub_issue_write |
Add, remove, or reprioritize a sub-issue |
CLI / REST API (write operations)
gh api performs the same writes and is the form used in the examples below. Reach for it when the MCP server is not connected, or when you need a REST field the MCP tools do not expose.
| Operation | Command |
|---|---|
| Create issue | gh api repos/{owner}/{repo}/issues -X POST -f title=... -f body=... |
| Update issue | gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f title=... -f state=... |
| Add comment | gh api repos/{owner}/{repo}/issues/{number}/comments -X POST -f body=... |
| Close issue | gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f state=closed |
| Set issue type | Include -f type=Bug in the create call (REST API only, not supported by gh issue create CLI) |
Note: gh issue create works for basic issue creation but does not support the --type flag. Use gh api when you need to set issue types.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/dependencies.md 1.8 KB
- references/images.md 4.7 KB
- references/issue-fields.md 7.6 KB
- references/issue-types.md 1.7 KB
- references/labels.md 5.2 KB
- references/milestones.md 2.4 KB
- references/projects.md 8.4 KB
- references/search.md 7.1 KB
- references/sub-issues.md 3.6 KB
- references/templates.md 1.4 KB
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.
- 3d ago Changed 2a32d53088e6
- 1mo ago Changed · +16 lines · +19 tokens per session 59f45b2b9acf
- 1mo ago First seen · 207 lines · 141 tokens per session scan A 7cd61254c848
github-issues is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 160 tokens to every session and 2,310 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to github-issues, differing in 33 lines, and is treated as a copy.
Other skills, from other repositories
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
predictable-revenue
Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B…
team-topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…
structured-plan-mode
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition. Use this skill to break down large features into manageable, well-documented tasks with clear dependencies, action items, and success criteria. The skill provides a structured template and…
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.
run
Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline (design hardening, tests green, code-review clean), scaling the machinery to the task's tier and asking at most one batched question. Auto-links the issue to close on merge, advances the board card…