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 lugassawan/swe-workbench --skill workflow-pr-reviewgit clone --depth 1 https://github.com/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/workflow-pr-review)<a href="https://agentmods.dev/skills/lugassawan/swe-workbench/workflow-pr-review"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/workflow-pr-review.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.00106 | $0.07069 |
| Opus 5 | $0.00053 | $0.03535 |
| Sonnet 5 | $0.00021 | $0.01414 |
| Haiku 4.5 | $0.00011 | $0.00707 |
Grade A, and why
workflow-pr-review 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 3d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: PR Review (remote-PR orchestration shell)
Announce at start: "I'm using the workflow-pr-review skill to review PR #N." (first-pass mode) or "...to re-check PR #N." (followup mode).
Mode resolution
This skill runs in one of two modes, chosen by the caller: first-pass (a fresh review) or followup (a re-check after the owner has addressed feedback). commands/review.md sets MODE=auto for a bare /swe-workbench:review <N> invocation and MODE=followup for --check-followup <N>. MODE=auto self-resolves to first-pass or followup at the top of Step 1 — see below — before mode-table interpolation happens, so everything downstream only ever sees a concrete first-pass/followup value.
Four values are derived from $MODE once, up front, and interpolated into every downstream bash block below — evaluated, not applied by hand:
| Var | first-pass |
followup |
|---|---|---|
MODE_TAG |
pr-review |
pr-followup |
STATE_SUFFIX |
(empty) | -followup |
CALLER_TAG |
general |
followup |
BYLINE |
_Reviewed by \reviewer`_` |
_Re-reviewed by \reviewer`_` |
The resolution itself happens at the top of Step 1 (the case "$MODE" block), which also echoes Mode: $MODE so mode selection is visible in the transcript — mirroring what commands/review.md already prints (Mode: <normalized-mode> (explicit) / Inferred mode: <mode> — reason: ...) for its own --mode selection.
When to invoke
- The user passes a PR number to
/swe-workbench:review(e.g./swe-workbench:review 123) — first-pass mode. - The user accepts the auto-detect prompt on
/swe-workbench:reviewno-arg ("Detected PR #N — review it? Replyyes") — first-pass mode. - The user runs
/swe-workbench:review --check-followup <N>— followup mode. - An agent or command needs to "review this remote PR end-to-end" — fetch + analyse + post + submit.
- Phrases (first-pass): "review PR 123", "do a peer review of #456", "fetch this PR and post deduped comments".
- Phrases (followup): "re-check PR 123", "check if my review comments were addressed", "follow up on review #456".
What ships with it
1 file 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.
- 3d ago Changed · +70 lines 96a0a20558f4
- 4d ago First seen · 219 lines · 106 tokens per session scan A 116f6b9ac0ec
workflow-pr-review is a skill published in the GitHub repository lugassawan/swe-workbench (2 stars, last pushed 2d ago), licensed MIT. It adds 106 tokens to every session and 7,069 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-09-03.
Other skills, from other repositories
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized…
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
review
Perform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when…
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…