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 agentmods add skills/grehnen/copilot-tooling/gh-sub-issuenpx skills add grehnen/copilot-tooling --skill gh-sub-issuegit clone --depth 1 https://github.com/grehnen/copilot-toolingWrote 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/grehnen/copilot-tooling/gh-sub-issue)<a href="https://agentmods.dev/skills/grehnen/copilot-tooling/gh-sub-issue"><img src="https://agentmods.dev/badge/skills/grehnen/copilot-tooling/gh-sub-issue.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 | $0.00050 | $0.00401 |
| Opus 5 | $0.00025 | $0.00200 |
| Sonnet 5 | $0.00010 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
gh-sub-issue 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 4d 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
gh-sub-issue
GitHub CLI extension for managing parent-child issue relationships. See EXAMPLES.md for workflows.
Command reference
| Command | Syntax | Key flags |
|---|---|---|
| add | gh sub-issue add <parent> <child> |
--repo |
| create | gh sub-issue create --parent <n> --title <t> |
--body --label --assignee --milestone --project --repo |
| list | gh sub-issue list <parent> |
--state {open|closed|all} --limit --json <fields> --web --repo |
| remove | gh sub-issue remove <parent> <child> [child...] |
--force --repo |
<parent> and <child> accept issue numbers or full GitHub URLs.
--json fields
number, title, state, assignees, labels, parent.number, parent.title, total, openCount
Troubleshooting
| Error | Fix |
|---|---|
| command not found | gh extension install yahsan2/gh-sub-issue |
| authentication required | gh auth login |
| permission denied | ensure write access to the repo |
Debug: GH_DEBUG=1 gh sub-issue list 123
Installation
gh extension install yahsan2/gh-sub-issue
gh extension upgrade sub-issue # update
What ships with it
1 file 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.
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.
- 4d ago First seen · 40 lines · 50 tokens per session scan A 6a68315969e8
gh-sub-issue is a skill published in the GitHub repository grehnen/copilot-tooling (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 401 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…