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 kBashar/myagentskills --skill review-resolvergit clone --depth 1 https://github.com/kBashar/myagentskillsWrote 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/kbashar/myagentskills/review-resolver)<a href="https://agentmods.dev/skills/kbashar/myagentskills/review-resolver"><img src="https://agentmods.dev/badge/skills/kbashar/myagentskills/review-resolver.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.00082 | $0.01272 |
| Opus 5 | $0.00041 | $0.00636 |
| Sonnet 5 | $0.00016 | $0.00254 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
review-resolver 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 8d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-resolver
Overview
Turn a PR's scattered review feedback into resolved code, safely and auditably. The flow is: gate the worktree → fetch all comments → investigate each in real code → present a triage table → resolve what the operator selects → verify resolution.
Core principle: investigate before judging, and let the operator decide what to fix. Never resolve a comment you haven't traced into the actual code, and never fix comments the operator didn't select.
Inputs
A GitHub PR URL (https://github.com/owner/repo/pull/123) or a bare number 123. A bare number resolves against the git repo in the current directory. The target project repo — where the code lives — must be the current directory (or pass its path as the second script argument).
Workflow
Create one todo per step.
Step 1 — Preflight: clean-tree gate + checkout (automated)
A clean git tree is a prerequisite. Run:
scripts/preflight.sh <pr-number-or-url> [repo-dir]
- Exit 3 = dirty worktree. STOP. Show the operator the printed
git statusand tell them to commit, stash, or discard. Do NOT proceed, do NOT stash on their behalf without being asked. - Exit 2 = not a git repo (wrong directory).
- Exit 0 = tree was clean and the PR branch is now checked out. Continue.
Step 2 — Fetch all comments (automated)
scripts/fetch-comments.sh <pr-number-or-url> [repo-dir]
Emits one JSON array covering all three GitHub feedback channels — inline (line-level code comments, with path+line+diff_hunk), review (summary bodies + verdict state), and issue (general conversation). Save it (e.g. to the scratchpad) and parse it. Thread replies via in_reply_to.
Filter out noise before triaging: skip nitpick/approval-only chatter and bot comments unless they raise a real concern. Keep every substantive comment.
Step 3 — Investigate each comment in the real code
For each substantive comment, do not take it at face value:
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.
- 8d ago First seen · 93 lines · 82 tokens per session scan A 94aca39661c7
review-resolver is a skill published in the GitHub repository kBashar/myagentskills (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,272 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.