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-pr-pickup-designated-branch-supersedegit 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-pr-pickup-designated-branch-supersede)<a href="https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/gh-pr-pickup-designated-branch-supersede"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/gh-pr-pickup-designated-branch-supersede/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-pr-pickup-designated-branch-supersede"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/gh-pr-pickup-designated-branch-supersede.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.00045 | $0.01321 |
| Opus 5 | $0.00023 | $0.00660 |
| Sonnet 5 | $0.00009 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
gh-pr-pickup-designated-branch-supersede 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Picking up an existing PR when the harness designates a different branch
Problem
A session is asked to "pick up PR #N and finish the tasks", but the execution harness (Claude Code on the web, GitHub-Action-spawned sessions, etc.) pre-designates a branch name for all pushes — different from PR #N's head branch — and forbids pushing anywhere else. Three tempting wrong moves:
- Push to the PR's own head branch anyway. Violates the harness branch contract; on some remotes (proxy-scoped credentials) the push is denied outright, or worse, silently allowed against the operator's intent.
- Start the designated branch from main. You re-implement or cherry-pick the PR's work; the diff review context, commit messages, and the PR's own handoff docs (often committed ON the PR branch) are lost.
- Rewrite the inherited commits (rebase --exec amend, squash locally) to satisfy a commit-signature/identity linter. The originals are already pushed on the open PR; rewriting forks the history and confuses the supersede story.
Fix — the supersede pattern
# 1. Base the designated branch ON the PR head (keeps its commits + docs)
git fetch origin <pr-head-branch> main
git checkout -B <designated-branch> origin/<pr-head-branch>
# 2. If main moved since the PR forked, merge it now (one conflict pass early)
git merge origin/main -m "Merge main into <topic> continuation"
# 3. ...finish the work, commit...
# 4. PUSH WITH AN EXPLICIT REFSPEC — see trap below
git push -u origin <designated-branch>
# 5. Open the superseding PR; body says "Supersedes #N" + what was added
# 6. Comment on #N pointing to the new PR, then close #N (draft, unmerged)
Trap: checkout -B onto a remote ref hijacks your upstream
git checkout -B <designated> origin/<pr-head-branch> sets the new branch's
upstream to origin/<pr-head-branch>. From then on a bare git push
(or pull) targets the ORIGINAL PR's branch — exactly what the harness
forbids — and git status -sb quietly shows
<designated>...origin/<pr-head-branch> [ahead N]. Always push with the
explicit form git push -u origin <designated-branch>; the -u repoints
the upstream at your own remote branch on first push.
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 · 112 lines · 45 tokens per session scan A 8d8cb73eafea
gh-pr-pickup-designated-branch-supersede is a skill published in the GitHub repository wan-huiyan/agent-traffic-control (3 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,321 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
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.
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.
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.
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.