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 agentmods add skills/jl-cmd/claude-dev-env/orchestrator-refreshnpx skills add jl-cmd/claude-dev-env --skill orchestrator-refreshgit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWrote 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/jl-cmd/claude-dev-env/orchestrator-refresh)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/orchestrator-refresh"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/orchestrator-refresh.svg" alt="Measured on agentmods" 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 | $0.00073 | $0.01509 |
| Opus 5 | $0.00036 | $0.00754 |
| Sonnet 5 | $0.00015 | $0.00302 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
orchestrator-refresh 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 yesterday.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Refresh
Name the session identity first (see
../orchestrator/reference/host-detect.md).
Re-assert the discipline for that host only.
0. status_gate first (deterministic)
Script home (prefer install path, else package checkout):
%USERPROFILE%/.claude/skills/orchestrator/scripts/status_gate.py~/.claude/skills/orchestrator/scripts/status_gate.pyskills/orchestrator/scripts/status_gate.py
Pass the same --run-slug used at activate, if any.
0a. begin-firing (consume prior re-arm)
python <status_gate.py> begin-firing [--run-slug SLUG]
| Exit | Action |
|---|---|
| 1 | End the refresh. Cancel matching host schedules for /orchestrator-refresh if the host allows. Report inactive/done. Do not re-arm. Do not spawn. Any work already in flight keeps running. |
| 0 | Latch cleared. Continue with steps 1–6. |
0b. Done after ledger (step 1)
After ledger reconcile: if every task is completed/cancelled and no executor is running:
python <status_gate.py> set --status done [--run-slug SLUG]
Cancel matching host schedules; stop without re-arming.
The refresh never interrupts the run
A refresh firing reinforces discipline alongside work already in flight. It never pauses, cancels, or waits on a running executor. Reconcile the ledger, re-assert the routing, re-arm once, and hand control straight back to the work in progress.
Inside the re-arm protocol (step 6), every "stop" ends the re-arm and
nothing else. A should-reschedule exit 1 means no schedule is created this
firing, and a claim-rearm exit 1 means the schedule just created is
cancelled; either way the session keeps orchestrating in the same turn.
Two stops end the whole firing, and both leave running executors alone:
begin-firing exit 1 (step 0a) and the done branch (step 0b). Each means the
run is finished, not active, or has no readable status file, so the refresh
reports and adds nothing further.
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.
- yesterday Changed · -18 lines · +4 tokens per session b303d0de3ea9
- 4d ago First seen · 152 lines · 69 tokens per session scan A 2131c6dec256
orchestrator-refresh is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,509 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…