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 isolate-subagent-verification-from-live-worktreegit 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/isolate-subagent-verification-from-live-worktree)<a href="https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/isolate-subagent-verification-from-live-worktree"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/isolate-subagent-verification-from-live-worktree/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/isolate-subagent-verification-from-live-worktree"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/isolate-subagent-verification-from-live-worktree.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.00342 | $0.01567 |
| Opus 5 | $0.00171 | $0.00783 |
| Sonnet 5 | $0.00068 | $0.00313 |
| Haiku 4.5 | $0.00034 | $0.00157 |
Grade A, and why
isolate-subagent-verification-from-live-worktree 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 9d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A verifying agent in your live worktree measures your uncommitted work
Problem
You dispatch a subagent to verify a merge: "run the four suites and the validator against
main, report the numbers." You point it at the worktree you are working in, because that
is where the venv is symlinked and the tooling is set up.
Then you keep working — editing, staging, committing, merging PRs.
The agent's gate run measures the branch plus whatever is in your working tree at that instant. There is no clobber, no error, and nothing looks wrong: the suites really execute, the numbers it reports are real numbers, and it prints them with a commit SHA next to them. They are simply counts of a tree that exists only on your disk and will never be merged.
The report then becomes the session's evidence — pasted into a PR body, a handoff, a tracker
card — as "verified green at <sha>".
Why this is worse than the clobber cases
The sibling failures in this collection are loud once you look:
dispatched-bash-agent-git-checkout-clobbers-uncommitted-edit— your edit vanishes.concurrent-session-checkout-clobbers-shared-worktree— the branch changes under you.subagent-read-stale-worktree-needs-head-pin— the agent's cited lines contradict yours.
Here nothing contradicts anything. The only signal is a total that does not reconcile with the same command run at a different moment — and totals move for legitimate reasons all day in a repo with parallel sessions, so the delta reads as normal churn.
Context / trigger conditions
- You dispatched an agent to "verify", "run the gates", "confirm main is green", or "check the suite counts", and its prompt named a worktree path you are also using.
- An agent's reported total disagrees with your own run of the same command, with no merge in between to explain it.
- An agent mentions, in passing, that the working tree was modified with files it did not
write, or that
HEADmoved mid-run. - A
git statusin the agent's transcript is non-empty when you expected a clean tree. - You are about to publish "verified at
<sha>" using numbers gathered while you had unstaged edits.
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.
- 9d ago First seen · 127 lines · 342 tokens per session scan A 4a2a7772b9e1
isolate-subagent-verification-from-live-worktree is a skill published in the GitHub repository wan-huiyan/agent-traffic-control (3 stars, last pushed 4d ago), licensed MIT. It adds 342 tokens to every session and 1,567 once invoked, about $0.0017 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.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
bun-test-basics
Use for bun:test syntax, assertions, describe/it, test.skip/only/each, and basic patterns.
precommit
Pre-commit checks — lint:fix -> build -> test.
precommit-fast
Quick pre-commit checks — lint:fix -> test.
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…