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 tomzx/agents --skill check-linked-prgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/check-linked-pr)<a href="https://agentmods.dev/skills/tomzx/agents/check-linked-pr"><img src="https://agentmods.dev/badge/skills/tomzx/agents/check-linked-pr/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/tomzx/agents/check-linked-pr"><img src="https://agentmods.dev/badge/skills/tomzx/agents/check-linked-pr.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.00050 | $0.01994 |
| Opus 5.5 | $0.00020 | $0.00798 |
| Sonnet 5.5 | $0.00010 | $0.00399 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
check-linked-pr 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 22d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Linked PR
Detects pull requests authored by someone else that have been linked to a GitHub issue, and helps decide what to do about them.
Unlike check-duplicates (a one-time pre-flight check run before any work starts), this skill is meant to run repeatedly during an in-progress SDLC flow to catch a competing PR that appears after work has already begun.
It is read-only with respect to GitHub: it never comments, labels, or opens anything.
The only side effect is updating .sdlc/state.yml to remember which PRs the user already decided to ignore (so the recurring check does not re-prompt every phase).
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, target the issue from
$ISSUE_NUMBER(and$REPO), then from.sdlc/state.ymlgithub_ref. ghCLI authenticated with read access to the target repository.- A GitHub issue number to check.
If the feature has no issue yet (a
p-prefixed feature), there is nothing to link to: report clear and stop.
What counts as "linked"
A PR is considered linked to the issue when GitHub records a connection. The skill checks, in order of reliability:
- The issue timeline
cross-referenced/connectedevents whose source is a pull request (covers manual "Development" links, PRs that reference the issue number in their body, andcloses #N/fixes #Nkeywords). - A keyword search of open PRs mentioning the issue number (fallback when timeline is empty or unavailable).
A PR is excluded (not competing) when any of these hold:
- It is authored by the current authenticated user (
@me) — that is the SDLC flow's own PR. - Its number matches the SDLC flow's own PR (the PR number recorded in
.sdlc/state.ymlgithub_refoncecreate-prhas run). - Its number is listed in
linked_prs_acknowledgedin.sdlc/state.yml(the user already chose to ignore it this run).
Only open PRs from other authors count as competing. A merged PR means the issue may already be resolved: surface it separately as a signal that the flow may be obsolete.
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.
- 22d ago Changed · +13 lines 627b3b3c8abc
- 2mo ago First seen · 153 lines · 50 tokens per session scan A 006c260f6b79
check-linked-pr is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,994 once invoked, about $0.0002 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.