github-issues

github-issues is a skill for Claude Code, Codex from cyborg-garden/hermes-agent-mt. It costs 20 tokens per session (2,806 once invoked), scanned C, a copy of github-issues, MIT.

A guide for managing GitHub issues, which are tracked records of bugs, tasks, or requests in a repository. It covers creating, searching, sorting, labeling, assigning, and triaging them.

In plain words
What is it for?
It helps create issues, find relevant work, mark bugs, add labels, assign owners, and organize the issue queue.
Why use it?
It helps turn an unorganized list of GitHub work items into tasks that can be found and managed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps create issues, find relevant work, mark bugs, add labels, assign owners, and organize the issue queue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cyborg-garden/hermes-agent-mt/github-issues
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 cyborg-garden/hermes-agent-mt --skill github-issues
Clone the repo
git clone --depth 1 https://github.com/cyborg-garden/hermes-agent-mt

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/cyborg-garden/hermes-agent-mt/github-issues/github.svg)](https://agentmods.dev/skills/cyborg-garden/hermes-agent-mt/github-issues)
Your own site
<a href="https://agentmods.dev/skills/cyborg-garden/hermes-agent-mt/github-issues"><img src="https://agentmods.dev/badge/skills/cyborg-garden/hermes-agent-mt/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/cyborg-garden/hermes-agent-mt/github-issues"><img src="https://agentmods.dev/badge/skills/cyborg-garden/hermes-agent-mt/github-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,806 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% 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.1 $0.00020 $0.02806
Opus 5.5 $0.00008 $0.01122
Sonnet 5.5 $0.00004 $0.00561
Haiku 4.5 $0.00002 $0.00281

Measured 1mo ago against content hash c1be1ca373ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then

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

83% identical to github-issues — 20 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/github-issues/SKILL.md · 371 lines

How it starts

The opening of the file, as written. The whole thing — 371 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')
    elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then
      GITHUB_TOKEN=$(grep "github.com" ~/.git-credentials 2>/dev/null | head -1 | sed 's|https://[^:]*:\([^@]*\)@.*|\1|')
    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 · 371 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. 1mo ago First seen · 371 lines · 20 tokens per session scan C c1be1ca373ad

Subscribe to this mod's changes

github-issues is a skill published in the GitHub repository cyborg-garden/hermes-agent-mt (14 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 2,806 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). It is 83% identical to github-issues, differing in 20 lines, and is treated as a copy.

Related

Other skills, from other repositories

handoff-resume

Resume in-progress coding work across sessions from a HANDOFF.md and a dirty git working tree. Use when a task says "continue from HANDOFF.md", "retomar o processamento", or when picking up a repo mid-change with uncommitted edits and an open PR. Covers reading continuity docs, reconciling the real tree, decoding repo…

pedroiff0/awesome-skills · 95 tokens

github-issue-to-pr

Carry a GitHub issue to a verified PR with honest CI state.

ggg123124/vrchat-assistant · 20 tokens

pipeline-conductor

Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.

kirodotdev/KiroCrew · 65 tokens

github

Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.

AtomicBot-ai/atomic-agent · 48 tokens

mnemosyne-memory-override

Stricter, user-selected override that forces Mnemosyne for all durable memory storage, including small standing rules. Apply it only when the user has consciously chosen this policy; installation, this skill appearing in the skills index, or an ordinary memory task is not that choice. Without it, the default applies…

mnemosyne-oss/mnemosyne · 101 tokens

create-milestone

Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.

agentic-community/mcp-gateway-registry · 64 tokens