github-issues

github-issues is a skill for Claude Code from HezaoHezao/poirot. It costs 20 tokens per session (1,197 once invoked), scanned C, original, MIT.

A guide to managing GitHub Issues, which are GitHub’s system for reporting bugs, requesting work, and tracking tasks. It uses the GitHub command-line tool or the GitHub API.

In plain words
What is it for?
Use it to review open issues, create bug reports or tasks, organize them with labels, and assign them to people.
Why use it?
It gives you repeatable commands for finding, creating, sorting, labeling, and assigning issues instead of handling each task manually in the browser.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: built for hermes-agent.

Good fit Use it to review open issues, create bug reports or tasks, organize them with labels, and assign them to people.

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

Made for: Claude Code.

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/hezaohezao/poirot/github-issues/github.svg)](https://agentmods.dev/skills/hezaohezao/poirot/github-issues)
Your own site
<a href="https://agentmods.dev/skills/hezaohezao/poirot/github-issues"><img src="https://agentmods.dev/badge/skills/hezaohezao/poirot/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/hezaohezao/poirot/github-issues"><img src="https://agentmods.dev/badge/skills/hezaohezao/poirot/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 1,197 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 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.00020 $0.01197
Opus 5.5 $0.00008 $0.00479
Sonnet 5.5 $0.00004 $0.00239
Haiku 4.5 $0.00002 $0.00120

Measured 1mo ago against content hash 0f8b7bd3b842, 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

# With curl curl -s "https://api.github.com/repos/$OWNER/$REPO/issues?state=open&per_page=20" | python3 -c "

Makes network callslowCapability

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

then `curl` fallback.
poirot/backend/agents/skill/builtin_skills/software-development/github-issues/SKILL.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 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 curl fallback.

Prerequisites

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

Setup

if command -v gh &>/dev/null && gh auth status &>/dev/null; then
  AUTH="gh"
else
  AUTH="curl"
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 --state open --limit 20
gh issue view 42

# With curl
curl -s "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):
    print(f'#{i[\"number\"]:4d} [{i[\"state\"]:6s}] {i[\"title\"][:60]}')
"

2. Creating Issues

# With gh (interactive editor)
gh issue create

# With gh (inline)
gh issue create --title "Bug: login fails on Safari" --body "Description..."

# With curl
curl -s -X POST \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues \
  -d '{"title":"Bug: login fails","body":"Description","labels":["bug"]}'

3. Searching Issues

# Search within repo
gh issue list --search "login error" --state all

# Search across GitHub
gh search issues "is:issue is:open repo:$OWNER/$REPO label:bug"

# With curl (GitHub Search API)
curl -s "https://api.github.com/search/issues?q=repo:$OWNER/$REPO+label:bug+state:open" | python3 -c "
import sys, json
r = json.load(sys.stdin)
print(f'Total: {r[\"total_count\"]}')
for i in r['items']:
    print(f'#{i[\"number\"]:4d} {i[\"title\"][:60]}')
"

4. Labels

# List labels
gh label list

# Create label
gh label create "priority-high" --color "D73A4A" --description "High priority"

# Add label to issue
gh issue edit 42 --add-label "priority-high"

# With curl
curl -s -X POST \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42/labels \
  -d '{"labels":["priority-high"]}'

Read the full file on GitHub · 169 lines

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 · 169 lines · 20 tokens per session scan C 0f8b7bd3b842

Subscribe to this mod's changes

github-issues is a skill published in the GitHub repository HezaoHezao/poirot (251 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 1,197 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

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

babysit

Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.

kirodotdev/KiroCrew · 45 tokens

feature-request

Conversational workflow for gathering user feedback and filing GitHub Issues on the Kiro Crew repository. Load when the user clicks "Request a Feature", wants to report a bug, or suggest an improvement.

kirodotdev/KiroCrew · 43 tokens

goal-loop

Bootstrap a goal-driven self-improving AutoNudge loop from a goal plus an anchor directory, then run the board autonomously until the Definition of Done is met.

kirodotdev/KiroCrew · 37 tokens

team-lead

Run a goal as a team when you can also do the work yourself: decide what you keep, dispatch the rest, and keep the status board honest. The delta over goal-conductor, which carries the dispatch, patrol and acceptance procedure this one points at. Load it when you are handed a goal, not a task.

kirodotdev/KiroCrew · 69 tokens

goal-ledger-conductor

Deprecated alias of goal-conductor, removed next release. The work-ledger conducting procedure now lives in goal-conductor; read that skill instead.

kirodotdev/KiroCrew · 35 tokens