github-issues

github-issues is a skill for Claude Code, Codex from IBM/mcp-context-forge. It costs 33 tokens per session (336 once invoked), scanned A, original, Apache-2.0.

A set of rules and procedures for creating, labeling, and organising GitHub issues. GitHub issues are repository records used to track bugs, tasks, and planned changes.

In plain words
What is it for?
Use it to open or update epics, features, stories, tasks, bugs, chores, and documentation issues, including links between parent and child issues.
Why use it?
It keeps issue titles, labels, issue types, relationships, and status changes consistent. This makes work easier to triage and connect across larger pieces of work.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

Good fit Use it to open or update epics, features, stories, tasks, bugs, chores, and documentation issues, including links between parent and child issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ibm/mcp-context-forge/github-issues
About the project

ContextForge is an open-source gateway and registry that brings MCP, A2A, REST, and gRPC tools, agents, and APIs together behind one endpoint. It helps teams discover, govern, observe, authenticate, and route calls across AI infrastructure. The catalogue add-ons support operating and extending this gateway.

IBM/mcp-context-forge · 4,832 stars · on GitHub · ibm.github.io

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 IBM/mcp-context-forge --skill github-issues
Clone the repo
git clone --depth 1 https://github.com/IBM/mcp-context-forge

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 github-issues

README.md
[![agentmods](https://agentmods.dev/badge/skills/ibm/mcp-context-forge/github-issues/github.svg)](https://agentmods.dev/skills/ibm/mcp-context-forge/github-issues)
Your own site
<a href="https://agentmods.dev/skills/ibm/mcp-context-forge/github-issues"><img src="https://agentmods.dev/badge/skills/ibm/mcp-context-forge/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.

agentmods 80×15 button for github-issues

Your own site · 80×15
<a href="https://agentmods.dev/skills/ibm/mcp-context-forge/github-issues"><img src="https://agentmods.dev/badge/skills/ibm/mcp-context-forge/github-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 336 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.00033 $0.00336
Opus 5.5 $0.00013 $0.00134
Sonnet 5.5 $0.00007 $0.00067
Haiku 4.5 $0.00003 $0.00034

Measured today against content hash 64f5873026c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

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.

.agents/skills/github-issues/SKILL.md · 15 lines

What it actually says

GitHub Issues

  • Start from the matching template in .github/ISSUE_TEMPLATE/. The template sets the GitHub Issue Type (Epic, Feature, Story, Task, Bug). The template's sections define the body.
  • Hierarchy: an Epic holds Features, a Feature holds Stories, a Story holds Tasks. Link children with GitHub sub-issues on the parent. Bugs stand alone or nest anywhere in that chain.
  • Titles carry no type prefix. Write a plain imperative summary: Gateway drops WebSocket sessions on restart.
  • Labels carry no issue types. New issues start with triage. The Chore and Documentation templates also apply chore and documentation. Add 1-3 optional scope labels (security, performance, ui, api, python, devops, a2a, mcp-protocol).
  • The organization defines the issue type names. Template type values must match those names exactly.
  • Lifecycle labels: awaiting-user when blocked on reporter feedback, blocked for dependency blockers, planned when accepted but deferred, fixed only after the resolving change merges.
  • Bodies and comments follow Agent Prose in AGENTS.md. Before you post, rewrite them with the asd-ste100 skill in STE-flavored mode. For public tone, see the pr-review skill, section Tone.
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. today First seen · 15 lines · 33 tokens per session scan A 64f5873026c0

Subscribe to this mod's changes

github-issues is a skill published in the GitHub repository IBM/mcp-context-forge (4,832 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 336 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-11-17.

Related

github-issues compared with skills from other repositories

github-issues next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
github-issuesIBM/mcp-context-forgeSkill4.8ktodayApache-2.0A33Claude Code, Codex
cis-aws-foundations-4.10CyberStrikeus/CyberStrikeSkill3.6ktodayAGPL-3.0A22Claude Code, Codex
rowboat-spacesrowboatlabs/rowboatSkill18kyesterdayApache-2.0A60Claude Code, Codex
create-tech-designhumanlayer/humanlayerSkill13kyesterdayApache-2.0A16Claude Code, Codex
deploy-docker-composeomnigent-ai/omnigentSkill11ktodayApache-2.0A84Claude Code, Codex
haikuagno-agi/agnoSkill43ktodayApache-2.0A0Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skillsSkill3.2ktodayMITA78Claude Code