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 multi-worktree-file-url-stale-contentgit 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/multi-worktree-file-url-stale-content)<a href="https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/multi-worktree-file-url-stale-content"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/multi-worktree-file-url-stale-content/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/multi-worktree-file-url-stale-content"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/multi-worktree-file-url-stale-content.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.00257 | $0.02172 |
| Opus 5 | $0.00129 | $0.01086 |
| Sonnet 5 | $0.00051 | $0.00434 |
| Haiku 4.5 | $0.00026 | $0.00217 |
Grade A, and why
multi-worktree-file-url-stale-content 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 10d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-worktree file:// URL stale content
Problem
The user opens a file:// URL pointing to a deliverable / static HTML / docs file in the repo. They see old content. They report "the fix isn't there" or "I still see the thing we removed". They are correct about what they see — but the file IS fixed on origin/main. The disconnect is that the file:// URL doesn't know what git branch is checked out at that path. The browser just reads whatever bytes are on disk.
In a repo with multiple git worktree checkouts, each worktree is on a different branch. The primary checkout at the repo root is also on a branch — usually the last feature branch someone was working on, NOT main. After a PR merges to main, none of the on-disk paths automatically update. The user's bookmark keeps showing the same stale content.
Context / Trigger Conditions
All of:
- Repo uses git worktrees (
git worktree listshows 2+ entries) - File in question is a deliverable / static asset / docs file that humans open directly (HTML, MD-rendered-to-HTML, JSON viewer, PDF), not a service-rendered URL
- User opens it via
file://URL bookmark (not via a running web server, not via VSCode preview) - Recent merge to main updated that file
- User reports the file looks wrong / old / unchanged
Smoking-gun signal: the user-reported file path contains .claude/worktrees/<name>/, worktrees/, .git/worktrees/, or you can see 2+ worktrees via git worktree list and the bookmarked path is one of them.
Solution
Step 1 — confirm the file is actually fixed on main
# 1. Fresh fetch (don't trust cached refs)
git fetch origin main --quiet
# 2. Read the file as it exists on origin/main
git show origin/main:<path-relative-to-repo-root> | grep -c "<the-string-the-user-says-is-still-there>"
# Expect 0 if the fix is in
If the fix IS on main but the user's view doesn't show it → confirmed stale-worktree problem.
Step 2 — identify which worktree the user's URL resolves to
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.
- 10d ago First seen · 142 lines · 257 tokens per session scan A 8fb7822a6d2b
multi-worktree-file-url-stale-content is a skill published in the GitHub repository wan-huiyan/agent-traffic-control (3 stars, last pushed 5d ago), licensed MIT. It adds 257 tokens to every session and 2,172 once invoked, about $0.0013 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
ql-housekeep
Detect repo-hygiene issues that accumulate during long-running autonomous development (merge-conflict markers, orphan worktrees, CPC-variant duplicates, stale branches, version-manifest drift). Detection-only by default — reports findings, never deletes or modifies without explicit user confirmation.
nazgul:doctor
Run the Nazgul read-only preflight diagnostic — checks jq/gh presence and auth, git-hooks drift, cache-vs-repo plugin version, the bash-vs-zsh hazard, the NAZGULDIR footgun, config-schema staleness, either install mode's .gitignore Nazgul-block drift (stamp and flush-left region), cross-session messaging and Remote…
hotfix
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
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.
cloudflare-workers-dev-experience
Cloudflare Workers local development with Wrangler, Miniflare, hot reload, debugging. Use for project setup, wrangler.jsonc configuration, or encountering local dev, HMR, binding simulation errors.