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.
git clone --depth 1 https://github.com/davekilleen/DexWrote 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/commands/davekilleen/dex/resolve_pr_parallel)<a href="https://agentmods.dev/commands/davekilleen/dex/resolve_pr_parallel"><img src="https://agentmods.dev/badge/commands/davekilleen/dex/resolve_pr_parallel/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/commands/davekilleen/dex/resolve_pr_parallel"><img src="https://agentmods.dev/badge/commands/davekilleen/dex/resolve_pr_parallel.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.00011 | $0.00288 |
| Opus 5.5 | $0.00004 | $0.00115 |
| Sonnet 5.5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
resolve_pr_parallel 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 1mo 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.
What it actually says
Resolve all PR comments using parallel processing.
Claude Code automatically detects and understands your git context:
- Current branch detection
- Associated PR context
- All PR comments and review threads
- Can work with any PR by specifying the PR number, or ask it.
Workflow
1. Analyze
Get all unresolved comments for PR
gh pr status
bin/get-pr-comments PR_NUMBER
2. Plan
Create a TodoWrite list of all unresolved items grouped by type.
3. Implement (PARALLEL)
Spawn a pr-comment-resolver agent for each unresolved item in parallel.
So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this
- Task pr-comment-resolver(comment1)
- Task pr-comment-resolver(comment2)
- Task pr-comment-resolver(comment3)
Always run all in parallel subagents/Tasks for each Todo item.
4. Commit & Resolve
- Commit changes
- Run bin/resolve-pr-thread THREAD_ID_1
- Push to remote
Last, check bin/get-pr-comments PR_NUMBER again to see if all comments are resolved. They should be, if not, repeat the process from 1.
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.
- 1mo ago First seen · 50 lines · 11 tokens per session scan A 57f39ffef6cc
resolve_pr_parallel is a command published in the GitHub repository davekilleen/Dex (496 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 288 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
revert
Git-aware undo by logical work unit (track, phase, or task).
team-review
Launch a multi-reviewer parallel code review with specialized review dimensions.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.