gh-issues

An automation workflow for handling GitHub issues, which are reported tasks or bugs in a code repository. It uses the GitHub API, assigns implementation work to sub-agents, opens pull requests, and handles review feedback.

In plain words
What is it for?
Use it to fetch filtered issues, create fixes, open pull requests, monitor them, address reviews, or run the process in watch, scheduled, or dry-run modes.
Why use it?
It removes much of the repeated work involved in finding issues, implementing fixes, submitting changes, and responding to review comments.

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/google/adk-js/gh-issues
Any agent
npx skills add google/adk-js --skill gh-issues
Clone the repo
git clone --depth 1 https://github.com/google/adk-js

Made for: Claude Code, Codex.

Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,982 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin 100% 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.00116 $0.08982
Opus 5 $0.00058 $0.04491
Sonnet 5 $0.00023 $0.01796
Haiku 4.5 $0.00012 $0.00898

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

Security

Grade A, and why

gh-issues scanned grade A with 1 finding 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.

Makes network callslowCapability

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

'requires': {'bins': ['curl', 'git', 'gh']},
Origin

This is a copy

100% identical to gh-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.

tests/integration/skills/skills/gh-issues/SKILL.md · 886 lines

How it starts

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

gh-issues — Auto-fix GitHub Issues with Parallel Sub-agents

You are an orchestrator. Follow these 6 phases exactly. Do not skip phases.

IMPORTANT — No gh CLI dependency. This skill uses curl + the GitHub REST API exclusively. The GH_TOKEN env var is already injected by OpenClaw. Pass it as a Bearer token in all API calls:

curl -s -H "Authorization: Bearer $GH_TOKEN" -H "Accept: application/vnd.github+json" ...

Phase 1 — Parse Arguments

Parse the arguments string provided after /gh-issues.

Positional:

  • owner/repo — optional. This is the source repo to fetch issues from. If omitted, detect from the current git remote: git remote get-url origin Extract owner/repo from the URL (handles both HTTPS and SSH formats).

Flags (all optional):

Flag Default Description
--label (none) Filter by label (e.g. bug, enhancement)
--limit 10 Max issues to fetch per poll
--milestone (none) Filter by milestone title
--assignee (none) Filter by assignee (@me for self)
--state open Issue state: open, closed, all
--fork (none) Your fork (user/repo) to push branches and open PRs from. Issues are fetched from the source repo; code is pushed to the fork; PRs are opened from the fork to the source repo.
--watch false Keep polling for new issues and PR reviews after each batch
--interval 5 Minutes between polls (only with --watch)
--dry-run false Fetch and display only — no sub-agents
--yes false Skip confirmation and auto-process all filtered issues
--reviews-only false Skip issue processing (Phases 2-5). Only run Phase 6 — check open PRs for review comments and address them.
--cron false Cron-safe mode: fetch issues and spawn sub-agents, exit without waiting for results.
--model (none) Model to use for sub-agents (e.g. glm-5, zai/glm-5). If not specified, uses the agent's default model.
--notify-channel (none) Telegram channel ID to send final PR summary to (e.g. -1002381931352). Only the final result with PR links is sent, not status updates.

Read the full file on GitHub · 886 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. 2d ago First seen · 886 lines · 116 tokens per session scan A b5a6ee908aea

Subscribe to this mod's changes

gh-issues is a skill published in the GitHub repository google/adk-js (1,379 stars, last pushed today), licensed Apache-2.0. It adds 116 tokens to every session and 8,982 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to gh-issues, differing in 20 lines, and is treated as a copy.

Related

Other skills, from other repositories

invest-backfill

Survey an existing codebase and generate Investiture doctrine files — VECTOR.md, CLAUDE.md, ARCHITECTURE.md — by combining Investiture defaults with patterns inferred from the project. Run this once on a project that does not yet have doctrine. Then run invest-doctrine to validate what was generated.

celanthe/clarion · 66 tokens

invest-doctrine

Audit the doctrine files themselves — VECTOR.md, CLAUDE.md, ARCHITECTURE.md — for completeness, internal consistency, cross-document contradictions, and drift from the actual codebase. Run this before invest-architecture. The doctrine must be sound before you enforce it.

celanthe/clarion · 59 tokens

animate

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

celanthe/clarion · 25 tokens

delight

Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.

celanthe/clarion · 28 tokens

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.

celanthe/clarion · 47 tokens

harden

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

celanthe/clarion · 32 tokens