Borrowing it
Nothing to install: this file belongs to limehq/munkel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/limehq/munkel/main/.claude/skills/github-issue-workflow/SKILL.mdgit clone --depth 1 https://github.com/limehq/munkelWrote 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/limehq/munkel/github-issue-workflow)<a href="https://agentmods.dev/skills/limehq/munkel/github-issue-workflow"><img src="https://agentmods.dev/badge/skills/limehq/munkel/github-issue-workflow/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.
<a href="https://agentmods.dev/skills/limehq/munkel/github-issue-workflow"><img src="https://agentmods.dev/badge/skills/limehq/munkel/github-issue-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00948 |
| Opus 5.5 | $0.00024 | $0.00379 |
| Sonnet 5.5 | $0.00012 | $0.00190 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
github-issue-workflow 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Starting work on a GitHub issue
One issue → one owner → one draft PR, linked both ways. The point is that ownership and in-flight work are visible to everyone from the moment work starts, so two people never unknowingly build the same thing.
1. Before starting: is it already taken?
Never open a second branch or PR for an issue someone already owns. Check first:
gh issue view N # assignee + linked PRs
gh pr list --state open --search "N in:body" \
--json number,title,isDraft,url,headRefName
If the issue is already assigned, or an open PR (draft or not) already references it, it is taken. Stop — report what you found and coordinate with the owner, or pick a different issue. Do not start parallel work.
2. Claim the issue
Assignment is the ownership signal:
gh issue edit N --add-assignee @me # or the relevant GitHub login
3. Set up an isolated worktree, then open a draft PR immediately
Work in a dedicated git worktree, never the shared root checkout: another
Claude session may drive this checkout concurrently, and a stray checkout
between two of your commands silently moves HEAD — your commit then lands on
main instead of your branch. Branching from a freshly fetched origin/main
into a new worktree also gives you a clean, up-to-date starting point in one move.
Open the PR before the work is finished, so the issue↔PR link exists from the start. GitHub needs at least one commit on the branch to open a PR:
git fetch origin
git branch <type>/<short-slug> origin/main # feat/ fix/ docs/ chore/ refactor/
git worktree add .claude/worktrees/<type>+<slug> <type>/<short-slug> # slug = branch with / → +
cd .claude/worktrees/<type>+<slug> # stay here: run all edits, git, and builds from inside
git commit --allow-empty -m "chore: start #N" # or your first real commit
git push -u origin <type>/<short-slug>
gh pr create --draft --base main \
--title "<type>: <summary>" \
--body "Closes #N"
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.
- 1mo ago First seen · 85 lines · 60 tokens per session scan A 0ad543c3df9d
github-issue-workflow is a skill published in the GitHub repository limehq/munkel (23 stars, last pushed 27d ago), licensed MIT. It adds 60 tokens to every session and 948 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
autopilot-triage
Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.
create-pr
Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.
github-issue-lifecycle
A GitHub Issue workflow for taking a code change from request to review, approval, testing, and closure. It can also keep a GitHub Project board—the task board attached to a repository—in sync.
github-issues
Create, search, triage, label, assign, comment on, and close GitHub issues using the gh CLI, with a curl REST fallback.