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 aiya000/dotfiles --skill link-this-pr-to-issuegit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/aiya000/dotfiles/link-this-pr-to-issue)<a href="https://agentmods.dev/skills/aiya000/dotfiles/link-this-pr-to-issue"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/link-this-pr-to-issue/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/aiya000/dotfiles/link-this-pr-to-issue"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/link-this-pr-to-issue.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.00084 | $0.01774 |
| Opus 5.5 | $0.00034 | $0.00710 |
| Sonnet 5.5 | $0.00017 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
link-this-pr-to-issue 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRをIssueへDevelopmentでリンク
目的
PR本文へclosing keyword(Closes #N 等)を記載し、GitHubの「Development」欄にPRとIssueの相互リンクを確立する。これにより、PRがマージされたときに対象Issueが自動でクローズされる。
GitHubへの書き込み前に、必ず変更内容をユーザーへ提示して明示的な承認を得る。
入力
- PR番号またはURL。
#3797と3797の両形式を受け付ける。省略時は現在のブランチに紐づくPRを使う - Issue番号またはURL。省略時はPR本文から推測する(「2. 対象Issueを特定する」参照)
- 対象リポジトリ。省略時は現在のリポジトリを使う
手順
1. PRを特定する
- 対象リポジトリと
gh auth statusを確認する - PR番号が指定されていない場合は、
gh pr view --json number -q .numberで現在のブランチに紐づくPR番号を取得する gh pr view <PR> --json number,title,body,urlでPRのタイトル、本文、URLを取得する- PRを特定できない場合は、ユーザーにPR番号またはURLを確認する
2. 対象Issueを特定する
Issue番号が明示されている場合はそれを使う。省略された場合は、PR本文から次のパターンを大文字小文字を区別せず検索する。
Close #N、Closes #N、Closed #NFix #N、Fixes #N、Fixed #NResolve #N、Resolves #N、Resolved #NIssue: #N、- Issue: #N、関連 Issue: #Nなどの参照
- 1件見つかった場合は、それを対象Issueの候補とする
- 複数のIssue番号が見つかった場合は、どれをリンク対象にするかユーザーへ確認する
- 1件も見つからない場合は、ユーザーにIssue番号を確認する
- 対象番号がIssueであること(PRでないこと)を
gh api repos/{owner}/{repo}/issues/<番号> --jq '.pull_request == null'で確認する
3. 既存のリンク状態を確認する
GraphQLでPRの closingIssuesReferences を取得し、対象Issueが既にリンク済みかを判定する。
query($owner:String!,$repo:String!,$num:Int!){
repository(owner:$owner,name:$repo){
pullRequest(number:$num){
closingIssuesReferences(first:50){ nodes{ number title state } }
}
}
}
- 対象Issueが既に
closingIssuesReferencesに含まれる場合は、リンク済みと報告して終了する(冪等。本文を書き換えない) - 含まれない場合は次へ進む
4. PR本文の変更案を組み立てる
対象Issueに対する closing keyword 行を、PR本文へ追加または既存参照から変換する。
- closing keyword は原則
Closes #Nを使う。ただしIssueをクローズすべきでない場合(親Issueなど複数PRで解決する場合)は、ユーザーに意図を確認し、closing keyword ではなく通常参照(Related to #N)に留める判断を提示する - PR本文に既に対象Issueへの非closing参照(例:
- Issue: #N)がある場合は、その行を- Closes #Nに置換する - 参照行がない場合は、
### 関連するIssue・タスクセクションへ- Closes #Nを追記する - 当該セクションが存在しない場合は、既存本文を一切削除せず、本文末尾などの適切な位置に関連Issueの記述を追加する
- PR本文の他のセクションは変更しない
5. 差分を提示して承認を得る
次をユーザーへ提示する。
- 対象PRとIssueの番号・タイトル・URL
- PR本文の変更箇所(追加行または置換前後の行)だけを抜粋した差分
- リンクによりPRマージ時にIssueが自動クローズされること(closing keyword を使う場合)
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 · 115 lines · 84 tokens per session scan A 001e53944552
link-this-pr-to-issue is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 1,774 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
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.
write-ticket-description
Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation and for every rewrite of an existing issue's body — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without…
implement-unattended
Take a ticket whose approach and design are already approved through implementation, review and evidence to a draft PR, with nobody watching. Escalates decisions on the ticket and stops rather than choosing.
plan-unattended
Plan a ticket with nobody watching. Three independent discuss runs are reconciled into one approach and three design runs into one design, both are posted on the ticket, and implement-unattended is started in a new tmux window. Escalates on the ticket rather than taking a one-way decision.