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 merged-pr-not-deployed-gate-label-missinggit 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/merged-pr-not-deployed-gate-label-missing)<a href="https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/merged-pr-not-deployed-gate-label-missing"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/merged-pr-not-deployed-gate-label-missing/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/merged-pr-not-deployed-gate-label-missing"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/merged-pr-not-deployed-gate-label-missing.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.00401 | $0.04529 |
| Opus 5 | $0.00200 | $0.02264 |
| Sonnet 5 | $0.00080 | $0.00906 |
| Haiku 4.5 | $0.00040 | $0.00453 |
Grade A, and why
merged-pr-not-deployed-gate-label-missing 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 11d 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merged PR Not Deployed — Gate Label / Path Filter Quietly Skipped the Workflow
Problem
A code change is merged into main and CI is green. The user opens the live service expecting to see the change and it's not there. The natural first instinct is "Cloud Run is caching" or "the bake hasn't re-run yet" or "I'm looking at the wrong revision". The actual cause is much simpler and quieter: the deploy workflow never ran, because the PR didn't satisfy the workflow's if: gate (typically a required label like auto-deploy, or a path filter that excludes the changed files).
The trap is that GHA's conclusion=skipped looks visually identical to conclusion=success in the workflow run summary on the PR page and in gh run list — same green checkmark icon, same "completed" status. Nothing on the PR's "all checks passed" surface tells you the deploy didn't happen.
This is a sister symptom to gha-auto-deploy-never-ran-skipped-mask (the FIRST-time-the-gate-fires-and-finds-an-infra-gap pattern), but a distinct cause: here the gate works as designed, the PR simply didn't carry the label.
Context / Trigger Conditions
All of these are typically true:
-
The PR has been merged (
gh pr view <N> --json statereturnsMERGED). -
All required status checks were green at merge time.
-
The repo has a deploy workflow with a top-level conditional gate. Common patterns:
on: pull_request: types: [closed] branches: [main] jobs: gate: if: > github.event.pull_request.merged == true && contains(github.event.pull_request.labels.*.name, 'auto-deploy')Or path-filter style:
on: pull_request: types: [closed] paths: - '<analytics_pkg>/cloudrun/<dashboard_app>/**' -
The user reports "I merged + CI green but I can't see the changes live" minutes-to-hours after merge (long enough that they've already eliminated obvious caching).
-
Sibling PRs from the same hour DID auto-deploy successfully — i.e. the workflow itself is healthy.
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.
- 11d ago First seen · 330 lines · 401 tokens per session scan A 928662298a36
merged-pr-not-deployed-gate-label-missing is a skill published in the GitHub repository wan-huiyan/agent-traffic-control (3 stars, last pushed 6d ago), licensed MIT. It adds 401 tokens to every session and 4,529 once invoked, about $0.0020 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
fix-ci-failures
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the gh CLI.
diagnose-deployment
Surfaces PAC CLI upload errors and Dataverse async operation errors, pattern-matches against a known failure catalog, and optionally auto-fixes identified issues. Use when asked to: "diagnose deployment", "debug deployment", "deployment failed", "show deployment errors", "fix deployment issues", "show upload logs"…
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
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.
cloudflare-workers-observability
Cloudflare Workers observability with logging, Analytics Engine, Tail Workers, metrics, and alerting. Use for monitoring, debugging, tracing, or encountering log parsing, metric aggregation, alert configuration errors.
bun-sveltekit
Use when building or running SvelteKit apps on Bun, including SSR, adapters, and Bun-specific APIs.