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.
npx skills add Azzygoatcoder/agent-useful-skills --skill issue-skillgit clone --depth 1 https://github.com/Azzygoatcoder/agent-useful-skillsWrote 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.
[](https://agentmods.dev/skills/azzygoatcoder/agent-useful-skills/issue-skill)<a href="https://agentmods.dev/skills/azzygoatcoder/agent-useful-skills/issue-skill"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/issue-skill.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00083 | $0.00673 |
| Opus 5 | $0.00042 | $0.00336 |
| Sonnet 5 | $0.00017 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
issue-skill scanned grade A with 0 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Issue — GitHub Issue 工作流
issue 是角色无关的（谁都能提），但「分诊/关闭」是 maintainer 专属。
场景判定
| 场景 | 触发 | 谁 | 动作 |
|---|---|---|---|
| A. 提 issue | "报 bug"/"提 feature" | 任何人 | gh issue create（按模板写清） |
| B. 分诊 | "看 issue"/"打标签"/"指派" | Maintainer / Owner | gh issue list + edit --add-label/--add-assignee |
| C. 处理闭环 | "处理 issue #N"/"关掉" | Maintainer / Owner | gh issue comment / close |
| D. issue→PR | "修这个 issue" | 有 push 或 fork | 建分支 → 改 → PR 引用 fixes #N |
场景 A：提 issue
gh issue create --title "..." --body "..."（或交互式gh issue create）- body 模板：
- bug：复现步骤 / 期望 vs 实际 / 环境版本
- feature：动机 / 建议方案 / 可选替代
- 报 issue URL
场景 B：分诊
gh issue list --state open --label "help wanted"
gh issue edit <N> --add-label "bug" --add-assignee @me
场景 C：处理闭环
gh issue comment <N> --body "..."
gh issue close <N> --reason completed # 或 not-planned
场景 D：issue → PR 闭环
gh issue develop <N>（自动建分支 + checkout，需 gh 较新版本；不支持则手建fix/<N>-...）- 改代码 → commit
- PR 标题/正文引用
fixes #N（合并自动关 issue） - 提 PR 走 pr-skill（角色判据：owner 直推 / contributor fork）
自进化日志
| 日期 | 学习来源 | 吸收的模式 |
|---|---|---|
| 2026-08-13 | 协作流梳理（pr/release 之后补 issue） | issue 角色无关（谁都能提），但 B/C 分诊处理是 maintainer 专属；D 闭环复用 pr-skill 的 push 权限判据；fixes #N 让 PR 合并自动关 issue |
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.
- 8d ago First seen · 53 lines · 83 tokens per session scan A 4e7539d8e3aa
issue-skill is a skill published in the GitHub repository Azzygoatcoder/agent-useful-skills (6 stars, last pushed 9d ago), licensed MIT. It adds 83 tokens to every session and 673 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
friction-log
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".