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 wan-huiyan/agent-traffic-control --skill gh-squash-merge-closes-only-one-issuegit clone --depth 1 https://github.com/wan-huiyan/agent-traffic-controlWrote 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/wan-huiyan/agent-traffic-control/gh-squash-merge-closes-only-one-issue)<a href="https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/gh-squash-merge-closes-only-one-issue"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/gh-squash-merge-closes-only-one-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/wan-huiyan/agent-traffic-control/gh-squash-merge-closes-only-one-issue"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/gh-squash-merge-closes-only-one-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.00307 | $0.01801 |
| Opus 5 | $0.00153 | $0.00901 |
| Sonnet 5 | $0.00061 | $0.00360 |
| Haiku 4.5 | $0.00031 | $0.00180 |
Grade A, and why
gh-squash-merge-closes-only-one-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 12d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub squash-merge auto-closes only one issue per PR
Problem
You shipped a fix PR that addresses 4 filed issues. PR title:
fix(dashboard): wire /actions segment tiles + plug 4 audit P0s (closes #447, #448, #449, #450)
PR body opens with:
Closes #447, #448, #449, #450 — the four template/route P0s from the audit.
PR squash-merges cleanly. CI green, branch deleted. You move on.
Later: gh issue list --state open shows #448, #449, #450 still OPEN. Only #447 got auto-closed. You spend a confused minute checking whether the fix actually shipped (it did) before realising the issues never closed.
Context / Trigger Conditions
All of:
- PR title or body includes a comma-separated
Closes #X, #Y, #Z(orFixes,Resolves) reference. - PR was squash-merged (regular merge has slightly different parsing but the same gotcha applies).
- After merge:
gh pr view N --json statereturnsMERGED, butgh issue view #YreturnsOPENfor the second-and-later issues. - The first issue in the comma list IS closed correctly — proves your "Closes" keyword wasn't malformed.
This is not about the issues' content / labels / state. The fix did ship. The auto-close parser just bound the keyword to one issue.
Solution
Path A — prevent (preferred, before merge)
Write one keyword per issue in the PR body. GitHub closes each:
## Summary
Bundles four P0 fixes from the 2026-05-07 audit.
Closes #447.
Closes #448.
Closes #449.
Closes #450.
Or comma-list with a keyword per item:
Closes #447, closes #448, closes #449, closes #450.
GitHub recognises close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved (any case). One keyword binds to the immediately-following issue ref; a bare comma + #N after it is a reference, not a close trigger.
Path B — recover (after merge)
If the PR is already merged with the broken comma-list pattern:
# Close each leftover issue with a reference comment
for issue in 448 449 450; do
gh issue close $issue \
--comment "Closed by PR #457 (squash-merge auto-close caught only one issue per PR)."
done
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.
- 12d ago First seen · 146 lines · 307 tokens per session scan A e961acb944da
gh-squash-merge-closes-only-one-issue is a skill published in the GitHub repository wan-huiyan/agent-traffic-control (3 stars, last pushed today), licensed MIT. It adds 307 tokens to every session and 1,801 once invoked, about $0.0015 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
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
bump-sdk-version
Bump the FutureSearch SDK version across all files. Use when releasing a new SDK version, updating version numbers, or the user says bump version, release, version bump.
pr-check
PR review compliance: fetch review comments from an open PR, categorize as resolved/unresolved/dismissed, critically evaluate fixable items, implement approved fixes, and reply inline. Pass --unattended to halt on human-judgment items (emitted as Pending-Human) instead of prompting via AskUserQuestion.
babysit
PR babysitter: monitors CI status, auto-rebases when behind, auto-fixes CI where possible, delegates review comment handling to dlc:pr-check, and re-requests review after fixes. Designed for /loop usage with Remote Control.
git-ops
Git hygiene: clean up merged branches, prune stale remotes, and verify repository state.