Borrowing it
Nothing to install: this file belongs to couimet/rangeLink. 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/couimet/rangeLink/main/.claude/skills/create-github-issue-hook/SKILL.mdgit clone --depth 1 https://github.com/couimet/rangeLinkWrote 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/couimet/rangelink/create-github-issue-hook)<a href="https://agentmods.dev/skills/couimet/rangelink/create-github-issue-hook"><img src="https://agentmods.dev/badge/skills/couimet/rangelink/create-github-issue-hook/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/couimet/rangelink/create-github-issue-hook"><img src="https://agentmods.dev/badge/skills/couimet/rangelink/create-github-issue-hook.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.00791 |
| Opus 5.5 | $0.00013 | $0.00316 |
| Sonnet 5.5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
create-github-issue-hook 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create-Github-Issue Hook (RangeLink)
Consulted automatically by /create-github-issue at its label-selection step. Adds rangeLink-only requirements on top of the base workflow. All creation mechanics stay in the base skill: draft parsing, repo resolution, issue creation, sub-issue and dependency linking. Do not re-implement any of that here.
Scope
This hook applies to issues created in couimet/rangeLink only. Read the issue URL returned by the base skill, which names the repository that actually received the issue. When the URL is not under https://github.com/couimet/rangeLink/, the hook does not apply: report that, then let the base skill continue with its generic label offer. The cross-repo article-registration issue that /release-prep creates in couimet/couimet.github.io carries no labels, so it skips this hook.
Required Labels
Every issue created in this repo must carry exactly one type:* label and exactly one priority:* label before it is reported as created.
When either required label is not already determined, ask the user to choose, present the catalogs below, and wait for the answer.
Type labels (pick ONE)
type:bug— Bug or defect in existing functionalitytype:chore— Maintenance or housekeepingtype:debt— Technical debt that needs addressingtype:docs— Documentation improvementstype:enhancement— New feature or enhancementtype:refactor— Code refactoring without behavior changetype:test— Test coverage improvements
Priority labels (pick ONE)
priority:critical— Must be fixed ASAPpriority:high— High prioritypriority:medium— Medium prioritypriority:low— Nice to have
Apply
Run the edit against the issue URL returned by the base skill:
gh issue edit "<ISSUE_URL>" --add-label "type:<chosen>" --add-label "priority:<chosen>"
Optional Scope Labels
Offer any that apply (optional, not required):
scope:core— rangelink-core-ts packagescope:vscode-ext— rangelink-vscode-extension packagescope:test-utils— rangelink-test-utils packagescope:tooling— Build tools, scripts, CI/CDscope:docs— Documentation files
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 · 77 lines · 32 tokens per session scan A 81d097de78b3
create-github-issue-hook is a skill published in the GitHub repository couimet/rangeLink (10 stars, last pushed 8d ago), licensed MIT. It adds 32 tokens to every session and 791 once invoked, about $0.0001 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-09-14.
Other skills, from other repositories
omh-research-department
This is a Hermes-native research-department workflow skill.
omh-agent-board
This is a Hermes-native agent-board workflow skill.
omh-cto-loop
This is an OMH cto-loop workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
work-summary
Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on, project health, what's blocked, where did I…
frontend-composition
Implement polished self-contained HTML interfaces with semantic structure, maintainable CSS, realistic content, and purposeful visual hierarchy.
evidence-citations
Anchor every claim in an explanation to file:line evidence you actually opened, and mark the difference between what you verified and what you inferred.