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/start-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/start-issue-hook)<a href="https://agentmods.dev/skills/couimet/rangelink/start-issue-hook"><img src="https://agentmods.dev/badge/skills/couimet/rangelink/start-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/start-issue-hook"><img src="https://agentmods.dev/badge/skills/couimet/rangelink/start-issue-hook.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.00026 | $0.00504 |
| Opus 5.5 | $0.00010 | $0.00202 |
| Sonnet 5.5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
start-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 2mo 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start-Issue Hook (RangeLink)
Consulted automatically by /start-issue during context gathering. Adds QA TC coverage awareness to every issue plan.
Additional Context Gathering
Read packages/rangelink-vscode-extension/qa/qa-test-cases.yaml to understand current TC coverage. Note which feature sections exist and the highest -NNN per slug. Optionally glob packages/rangelink-vscode-extension/src/__integration-tests__/suite/*.test.ts to map existing test IDs by slug — this helps the plan reference which TCs already exist vs which need drafting.
Additional Plan Requirements
The plan must include EITHER:
- A TC-definition step that invokes
/tcs-definitionto draft new or updated QA test cases — placed BEFORE implementation steps when feasible. - An explicit justification in "Assumptions Made" stating why TCs are not needed for this issue. Valid reasons: internal refactors that don't change user-visible behavior, tooling/infrastructure changes, CI/CD changes, documentation-only changes, dependency bumps with no behavioral impact, changes to
.claude/skills or agents that don't touch extension runtime code.
If the issue introduces, modifies, or fixes user-visible behavior (new features, changed commands, changed output, new settings, behavior-altering bug fixes), the TC-definition step is REQUIRED — do not skip with an assumption.
Where the Step Sits
Prefer placing /tcs-definition as the first plan step. The skill's draft phase is spec-elicitation — running it before implementation keeps the interview focused on what the feature should do rather than confirming what was built. The skill itself warns when the diff exceeds 1000 lines because the interview drifts from spec-elicitation to implementation-confirmation.
When the TC entries depend on implementation-defined details (schema, exact output format), move the /tcs-definition step after the implementation steps but still before /finish-issue.
The /tcs-definition step body should read:
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.
- 2mo ago First seen · 38 lines · 26 tokens per session scan A 542627827ad0
start-issue-hook is a skill published in the GitHub repository couimet/rangeLink (10 stars, last pushed 8d ago), licensed MIT. It adds 26 tokens to every session and 504 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-08-31.
Other skills, from other repositories
browser-qa-delivery
Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.
omh-agent-evaluation
This is a Hermes-native agent-evaluation workflow skill.
omh-verification-gate
This is an OMH verification-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
frontend-composition
Implement polished self-contained HTML interfaces with semantic structure, maintainable CSS, realistic content, and purposeful visual hierarchy.