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/couimet/rangelink/github-issuesnpx skills add couimet/rangeLink --skill github-issuesgit clone --depth 1 https://github.com/couimet/rangeLinkWhat 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.00033 | $0.00604 |
| Opus 5 | $0.00016 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
github-issues 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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Conventions
This skill defines the project-specific conventions for GitHub issues. Claude auto-consults this when creating or modifying issues.
Required Labels
ALL issues MUST have one type:* label AND one priority:* label. Optionally add scope:* labels for affected packages.
Type labels (required — pick ONE)
type:bug— Bug or defect in existing functionalitytype:enhancement— New feature or enhancementtype:debt— Technical debt that needs addressingtype:docs— Documentation improvementstype:refactor— Code refactoring without behavior changetype:test— Test coverage improvements
Priority labels (required — pick ONE)
priority:critical— Must be fixed ASAPpriority:high— High prioritypriority:medium— Medium prioritypriority:low— Nice to have
Scope labels (optional — pick any that apply)
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
Labels to avoid
Do NOT use GitHub's default labels: bug, enhancement, duplicate, invalid, wontfix, question, good first issue, help wanted.
Parent-Child Issues
Use the GraphQL addSubIssue mutation for native sub-issue relationships. Never rely only on text links in descriptions (e.g., "Parent: #47").
# Get node IDs
PARENT_ID=$(gh api repos/:owner/:repo/issues/$PARENT_NUM --jq '.node_id')
CHILD_ID=$(gh api repos/:owner/:repo/issues/$CHILD_NUM --jq '.node_id')
# Link using native API
gh api graphql -H "GraphQL-Features: sub_issues" -f query="
mutation {
addSubIssue(input: {issueId: \"$PARENT_ID\", subIssueId: \"$CHILD_ID\"}) {
clientMutationId
}
}
"
No References to Ephemeral Files
NEVER reference .scratchpads/, .claude-questions/, .commit-msgs/, or .breadcrumbs/ files in GitHub issue content. These files are local/ephemeral and not accessible from GitHub.
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.
- 2d ago First seen · 68 lines · 33 tokens per session scan A 042df3708631
github-issues is a skill published in the GitHub repository couimet/rangeLink (10 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 604 once invoked, about $0.0002 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
react-artifact
Author app-like designs in React/JSX and bundle them in-sandbox into the same single self-contained HTML artifact Design Studio delivers. Use when the design needs real state, complex interactivity, or component reuse beyond what vanilla JS comfortably handles.
mcpls
Install, configure, and run the mcpls CLI — a Rust binary bridging MCP to LSP that gives an agent compiler-grade code intelligence (hover, definitions, references, diagnostics, rename). Use when setting up or registering mcpls as an MCP server, writing or debugging an mcpls.toml, choosing CLI flags or MCPLS…
Ticket Specs
Create, regenerate, update, and review Xyne Spaces ticket Specifications by interviewing for requirement intent before drafting or writing the Specification.
explanation-document
Structure a codebase/schema explanation as a self-contained HTML document ordered for a READER — mental model and flows first, deep per-component reference last — not in the order you explored it.
dashboard-data
Build truthful self-contained dashboard snapshots from connected MCP/data tools or user-provided datasets. Use for /dashboard runs that query real metrics, render charts or operational summaries, and may be refreshed by scheduled jobs.
architecture-diagrams
Author architecture, ER, and flow diagrams as hand-written inline SVG inside a self-contained HTML page — no mermaid, no scripts, no CDN.