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/pr-loop-cloud-transportnpx skills add jl-cmd/claude-dev-env --skill pr-loop-cloud-transportgit 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/pr-loop-cloud-transport)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/pr-loop-cloud-transport"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/pr-loop-cloud-transport.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.00090 | $0.01977 |
| Opus 5 | $0.00045 | $0.00988 |
| Sonnet 5 | $0.00018 | $0.00395 |
| Haiku 4.5 | $0.00009 | $0.00198 |
Grade A, and why
pr-loop-cloud-transport 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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR-loop cloud transport
One workflow that makes a cloud session able to run the PR-loop skill family. A cloud session ships no gh binary and cannot fetch one, so every gh step in a PR-loop skill routes through the GitHub MCP tools; this skill is the setup and routing contract for that substitution. The same routing serves a session whose gh is present but unauthenticated, or authenticated as an account that cannot act on the PR's owner — a binary that cannot act on the PR is as unusable as a binary that is not there. The evidence base is docs/references/cloud-pr-loop-compatibility.md in the source repo — every rule here traces to a live probe, the operation inventory recorded there, or the auth rule the calling skills state.
Decide the transport first
Three checks, in order; the first failure routes to the cloud transport:
command -v gh— the binary exists.gh auth status— an active authenticated account exists; a non-zero exit fails the check.- Once the PR scope is resolved (owner and repo known):
gh api repos/<owner>/<repo> --jq .permissions.pushmust printtrue. Thepermissionsobject in that response reports the authenticated account's own rights on the repo,pushincluded (live probe: the Section 7 appendix row in the runbook), so one command proves the binary, the auth, and the account's write access together. An error, a 404, orfalsefails the check.
- All three pass → local session. Stop here; follow the calling skill's own steps unchanged.
- Any check fails → cloud transport. Run the workflow below, then follow the calling skill's steps with every
ghoperation swapped for its cloud path.
A read-scoped account passes checks 1 and 2 and fails check 3 — the PR-loop skills push fix commits, so push: false means the local path stalls at its first push while the MCP transport carries the run.
GitHub MCP substitution covers gh operations only. It does not make Claude-only slash commands (for example /code-review) runnable. Those steps go through the chain-spawn helper documented in worker-spawn.md (detect_host_profile + invoke_code_review). Transport (gh vs MCP) and harness (Claude vs third-party) are separate axes.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 105 lines · 90 tokens per session scan A e4266536a39b
pr-loop-cloud-transport is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,977 once invoked, about $0.0005 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…