github-issues

A tool for managing GitHub issues, which are tracked tasks, bugs, and requests in a code repository.

In plain words
What is it for?
Use it to create and organize issues, find existing reports, assign people, add labels, close work, and connect issues to pull requests.
Why use it?
It keeps issue search, triage, assignment, labeling, closing, and pull-request links in one workflow.

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/neolabs-systems/neoagent/github-issues
Any agent
npx skills add NeoLabs-Systems/NeoAgent --skill github-issues
Clone the repo
git clone --depth 1 https://github.com/NeoLabs-Systems/NeoAgent

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,803 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin unknown 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 $0.00050 $0.02803
Opus 5 $0.00025 $0.01401
Sonnet 5 $0.00010 $0.00561
Haiku 4.5 $0.00005 $0.00280

Measured 2d ago against content hash b7fffb99ca7d, 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.

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.

description: Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
server/catalog_sources/store-bundles/skills/github/github-issues/SKILL.md · 370 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 370 lines · 50 tokens per session scan C b7fffb99ca7d

Subscribe to this mod's changes

github-issues is a skill published in the GitHub repository NeoLabs-Systems/NeoAgent (23 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 50 tokens to every session and 2,803 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, 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

solopi-ai

通过 SoloPi 的机器可读 CLI 编译和执行 AI 验证计划,管理签名端侧 ExecuTorch 决策模型、持久设备池、无人值守任务、安卓设备、应用、动作、配置、用例步骤与交互录制、回放及性能历史、动态 Agent、批量与重复执行、性能监控、压力测试和证据。适用于需求/AC 到 Result Judge 三态结论、cloud/on-device 决策切换、模型发布门禁,以及 generation 租约的多设备 CI 执行。.

alipay/SoloPi · 127 tokens

Phone Use

MUST Load this skill for ANY task that involves GUI interaction or device control — opening apps, tapping, typing, scrolling, swiping, Back/Home/Recents, reading the screen, or any workflow that touches on-screen content. Load this even when the user does not explicitly mention the device — if the task implies a GUI…

niki914/zafiro · 76 tokens

use-appclaw-cli

Use the AppClaw CLI to run YAML flows, start the interactive TUI shell, explore apps, record/replay sessions, configure devices, and troubleshoot. Trigger for any request involving appclaw commands, device setup, .env configuration, running flows, vision setup, or debugging execution failures.

appclawhq/AppClaw · 66 tokens

release-new-version

Use when preparing a Zafiro release commit that requires syncing app/build.gradle.kts version fields with the latest GitHub release.

niki914/zafiro · 30 tokens

generate-appclaw-flow

Generate YAML flow files for AppClaw mobile automation. Handles structured steps, natural language steps, phased flows (setup/steps/assertions), variable and secret interpolation via .appclaw/env/, and validation. Trigger when the user wants to create, edit, or fix a YAML flow file for AppClaw.

appclawhq/AppClaw · 69 tokens

review-changes

Review code changes in the AppClaw repo for correctness, CLI/VSCode extension consistency, and YAML flow parsing regressions. Use this skill whenever the user says "review my changes", "check my changes", "validate changes", "does this break anything", "review the diff", or any variation of wanting to verify that…

appclawhq/AppClaw · 104 tokens