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 skills add yu-iskw/github-project-skills --skill gh-linking-branches-to-issuesgit clone --depth 1 https://github.com/yu-iskw/github-project-skillsWrote 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/yu-iskw/github-project-skills/gh-linking-branches-to-issues)<a href="https://agentmods.dev/skills/yu-iskw/github-project-skills/gh-linking-branches-to-issues"><img src="https://agentmods.dev/badge/skills/yu-iskw/github-project-skills/gh-linking-branches-to-issues/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/yu-iskw/github-project-skills/gh-linking-branches-to-issues"><img src="https://agentmods.dev/badge/skills/yu-iskw/github-project-skills/gh-linking-branches-to-issues.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.00025 | $0.00220 |
| Opus 5 | $0.00013 | $0.00110 |
| Sonnet 5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
gh-linking-branches-to-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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 35 lines · 25 tokens per session scan A 7d4b21547e0b
gh-linking-branches-to-issues is a skill published in the GitHub repository yu-iskw/github-project-skills (8 stars, last pushed 11d ago), with no licence file. It adds 25 tokens to every session and 220 once invoked, about $0.0001 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
standup-update
Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
machinist
Use Machinist to create, assign, monitor, and resume software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, lifecycle labels, direct runs, or managed queue.
github
GitHub CLI operations via gh for issues, PRs, Actions, releases, and REST/GraphQL API with --json/--jq parsing. Triggers on: "create an issue", "submit a PR", "check CI status", "why did CI fail", "merge a PR", or pasted GitHub URLs.