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-convergenpx skills add jl-cmd/claude-dev-env --skill pr-convergegit 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-converge)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/pr-converge"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/pr-converge.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.1 | $0.00087 | $0.06710 |
| Opus 5 | $0.00044 | $0.03355 |
| Sonnet 5 | $0.00017 | $0.01342 |
| Haiku 4.5 | $0.00009 | $0.00671 |
Grade A, and why
pr-converge 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 6d 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 — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Converge
A code-review ↔ bugteam ↔ Bugbot ↔ Copilot loop on a draft PR: the internal
code-review and bugteam passes drive the code to clean first, then Cursor
Bugbot and Copilot run as terminal confirmation gates, until all are clean on
the same HEAD and mergeable. On pacer=schedule_wakeup, one tick runs per
invocation and the next tick is scheduled. On pacer=portable, ticks run
continuously in-session (see
../../skills/_shared/pr-loop/portable-driver.md).
Transport check (before any GitHub step)
Run command -v gh; when it succeeds, run gh auth status; once the PR
scope is resolved, run gh api repos/<owner>/<repo> --jq .permissions.push
and take true as the pass. When any check fails, run the
pr-loop-cloud-transport skill first and route every gh operation in this
skill through its substitution matrix.
Pre-flight
Task list (step 1)
After down/opt-out flags are known, build the work list with
build_converge_task_list.py only (same script as autoconverge). Register every
task; final task is always all_runnable_reviews_clean_same_head. Complete
that final task only when every runnable review is CLEAN on the same HEAD.
On pacer=portable, open-run returns the same list.
Pacer selection
Scan the tool list for ScheduleWakeup. Record whether it is present, then
select the pacer:
python "$HOME/.claude/skills/_shared/pr-loop/scripts/select_converge_pacer.py" \
--skill pr-converge \
--has-workflow <0|1> \
--has-schedule-wakeup <0|1>
pacer=schedule_wakeup— native tick pacing viaScheduleWakeup(seeworkflows/schedule-wakeup-loop.md).pacer=portable— continuous in-session driver on../../skills/_shared/pr-loop/portable-driver.md. Do not abort becauseScheduleWakeupis missing.
Worktree isolation
When the tool list includes EnterWorktree, call it with no arguments before
any API call, file read, or edit. Agent-view sessions start in the shared
checkout; Bash (gh, git) does not auto-isolate. Do not proceed until the
working directory contains .claude/worktrees/. If EnterWorktree fails,
report the failure and stop.
What ships with it
60 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.
- .claude/CLAUDE.md 14 B
- AGENTS.md 1 B
- pr_converge_skill_constants/__init__.py 0 B runs code
- pr_converge_skill_constants/.claude/CLAUDE.md 14 B
- pr_converge_skill_constants/AGENTS.md 1 B
- pr_converge_skill_constants/constants.py 2.7 KB runs code
- reference/.claude/CLAUDE.md 14 B
- reference/AGENTS.md 1 B
- reference/convergence-gates.md 15 KB
- reference/examples.md 7.7 KB
- reference/fix-protocol.md 1.9 KB
- reference/ground-rules.md 2.0 KB
- reference/multi-pr-orchestration.md 12 KB
- reference/obstacles/.claude/CLAUDE.md 14 B
- reference/obstacles/AGENTS.md 1 B
- reference/obstacles/fix-post-replies.md 433 B
- reference/obstacles/fix-publish-summary.md 438 B
- reference/obstacles/fix-push.md 380 B
- reference/obstacles/fix-read-filelines.md 397 B
- reference/obstacles/fix-reset-state.md 393 B
- reference/obstacles/fix-resolve-threads.md 421 B
- reference/obstacles/fix-spawn-clean-coder.md 406 B
- reference/obstacles/fix-stage-commit.md 397 B
- reference/obstacles/fix-trigger-bugbot.md 401 B
- reference/obstacles/fix-write-test.md 424 B
- reference/per-tick.md 29 KB
- reference/progress-checklist.md 9.6 KB
- reference/state-schema.md 7.4 KB
- reference/stop-conditions.md 1.7 KB
- scripts/_pr_converge_path_setup.py 1.7 KB runs code
- scripts/.claude/CLAUDE.md 14 B
- scripts/AGENTS.md 1 B
- scripts/caller-window-pid.ps1 2.6 KB runs code
- scripts/check_bugbot_ci.py 9.4 KB runs code
- scripts/check_convergence_availability.py 10 KB runs code
- scripts/check_convergence_gates.py 10 KB runs code
- scripts/check_convergence_thread_gates.py 7.9 KB runs code
- scripts/check_convergence.py 34 KB runs code
- scripts/check_pending_reviews.py 4.8 KB runs code
- scripts/conftest.py 1.7 KB runs code
- scripts/cursor-agents-continue-caller.cmd 327 B runs code
- scripts/cursor-agents-continue-stop-others.ps1 573 B runs code
- scripts/cursor-agents-continue.ahk 6.4 KB
- scripts/cursor-agents-continue.cmd 106 B runs code
- scripts/fetch_copilot_reviews.py 4.0 KB runs code
- scripts/post_fix_reply.py 4.4 KB runs code
- scripts/pr_converge_scripts_constants/__init__.py 0 B runs code
- scripts/pr_converge_scripts_constants/.claude/CLAUDE.md 14 B
- scripts/pr_converge_scripts_constants/AGENTS.md 1 B
- scripts/pr_converge_scripts_constants/convergence_gate_constants.py 2.4 KB runs code
- scripts/pr_converge_scripts_constants/pr_converge_constants.py 3.4 KB runs code
- scripts/pr_converge_scripts_constants/reflow_skill_md_constants.py 600 B runs code
- scripts/README.md 3.6 KB
- scripts/reflow_skill_md.py 12 KB runs code
- scripts/test__pr_converge_path_setup.py 949 B runs code
- scripts/test_check_bugbot_ci.py 10 KB runs code
- scripts/test_check_convergence_availability.py 13 KB runs code
- scripts/test_check_convergence_codex.py 15 KB runs code
- scripts/test_check_convergence_contract.py 14 KB runs code
- scripts/test_check_convergence_fixture.py 5.4 KB runs code
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.
- 6d ago First seen · 470 lines · 87 tokens per session scan A 98a656efcf77
pr-converge is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 6,710 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.