github-issues

A guide for managing GitHub issues, which are tracked reports of bugs, tasks, or requested improvements. It explains how to create, search, review, sort, and update them using GitHub tools or the API.

In plain words
What is it for?
Finding issues by state, label, assignee, or search text; viewing issue details; and creating or managing issue records.
Why use it?
It makes issue work more consistent and helps keep bugs and tasks organized in the repository.

Skill for Claude CodeCodex

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/atlasomnia/hermes-custom-pack/github-issues
Any agent
npx skills add AtlasOmnia/hermes-custom-pack --skill github-issues
Clone the repo
git clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-pack

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,707 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod 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 $0.00024 $0.02707
Opus 5 $0.00012 $0.01354
Sonnet 5 $0.00005 $0.00541
Haiku 4.5 $0.00002 $0.00271

Measured 2d ago against content hash 0cb1d860a6bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

github-issues scanned grade C with 2 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 2d 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.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

# Plaintext ~/.git-credentials is intentionally not used; prefer `gh auth login` or GITHUB_TOKEN in .env

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Create, search, triage, and manage GitHub issues. Each section shows `gh` first, then the `curl` fallback.
Origin

This is a copy

86% identical to github-issues — 186 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.

skills/github-issues/SKILL.md · 383 lines

How it starts

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

GitHub Issues Management

Create, search, triage, and manage GitHub issues. Each section shows gh first, then the curl fallback.

Prerequisites

  • Authenticated with GitHub (see github-auth skill)
  • Inside a git repo with a GitHub remote, or specify the repo explicitly

Setup

if command -v gh &>/dev/null && gh auth status &>/dev/null; then
 AUTH="gh"
else
 AUTH="git"
 if [ -z "$GITHUB_TOKEN" ]; then
 if _hermes_env="${HERMES_HOME:-$HOME/.hermes}/.env"; [ -f "$_hermes_env" ] && grep -q "^GITHUB_TOKEN=" "$_hermes_env"; then
 GITHUB_TOKEN=$(grep "^GITHUB_TOKEN=" "$_hermes_env" | head -1 | cut -d= -f2 | tr -d '\n\r')
# Plaintext ~/.git-credentials is intentionally not used; prefer `gh auth login` or GITHUB_TOKEN in .env
 fi
 fi
fi

REMOTE_URL=$(git remote get-url origin)
OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's|.*github\.com[:/]||; s|\.git$||')
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -d/ -f2)

1. Viewing Issues

With gh:

gh issue list
gh issue list --state open --label "bug"
gh issue list --assignee @me
gh issue list --search "authentication error" --state all
gh issue view 42

With curl:

# List open issues
curl -s \
 -H "Authorization: token $GITHUB_TOKEN" \
 "https://api.github.com/repos/$OWNER/$REPO/issues?state=open&per_page=20" \
 | python3 -c "
import sys, json
for i in json.load(sys.stdin):
 if 'pull_request' not in i: # GitHub API returns PRs in /issues too
 labels = ', '.join(l['name'] for l in i['labels'])
 print(f\"#{i['number']:5} {i['state']:6} {labels:30} {i['title']}\")"

# Filter by label
curl -s \
 -H "Authorization: token $GITHUB_TOKEN" \
 "https://api.github.com/repos/$OWNER/$REPO/issues?state=open&labels=bug&per_page=20" \
 | python3 -c "
import sys, json
for i in json.load(sys.stdin):
 if 'pull_request' not in i:
 print(f\"#{i['number']} {i['title']}\")"

# View a specific issue
curl -s \
 -H "Authorization: token $GITHUB_TOKEN" \
 https://api.github.com/repos/$OWNER/$REPO/issues/42 \
 | python3 -c "
import sys, json
i = json.load(sys.stdin)
labels = ', '.join(l['name'] for l in i['labels'])
assignees = ', '.join(a['login'] for a in i['assignees'])
print(f\"#{i['number']}: {i['title']}\")
print(f\"State: {i['state']} Labels: {labels} Assignees: {assignees}\")
print(f\"Author: {i['user']['login']} Created: {i['created_at']}\")
print(f\"\n{i['body']}\")"

# Search issues
curl -s \
 -H "Authorization: token $GITHUB_TOKEN" \
 "https://api.github.com/search/issues?q=authentication+error+repo:$OWNER/$REPO" \
 | python3 -c "
import sys, json
for i in json.load(sys.stdin)['items']:
 print(f\"#{i['number']} {i['state']:6} {i['title']}\")"

Read the full file on GitHub · 383 lines

Files

What ships with it

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

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. 2d ago First seen · 383 lines · 24 tokens per session scan C 0cb1d860a6bc

Subscribe to this mod's changes

github-issues is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (55 stars, last pushed 18d ago), licensed MIT. It adds 24 tokens to every session and 2,707 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). It is 86% identical to github-issues, differing in 186 lines, and is treated as a copy.