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/dropelikeit/pr-comments-resolver/resolve-commentsnpx skills add Dropelikeit/pr-comments-resolver --skill resolve-commentsgit clone --depth 1 https://github.com/Dropelikeit/pr-comments-resolverWhat 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.00039 | $0.03592 |
| Opus 5 | $0.00019 | $0.01796 |
| Sonnet 5 | $0.00008 | $0.00718 |
| Haiku 4.5 | $0.00004 | $0.00359 |
Grade A, and why
resolve-comments 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 2d 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve PR/MR Review Comments
Work through all unresolved review comments from a pull request or merge request on GitHub, GitLab, Bitbucket Cloud, or Azure DevOps.
This skill activates implicitly when its description matches your request. You can also reference it explicitly by name.
Step 0: Graphify Availability (mandatory if present)
Before anything else, check whether the Graphify skill is available in the running agent for this project.
These harnesses do not expose a skills registry. Treat Graphify as available only if the project clearly ships it (e.g. a graphify skill/command file under the project's skills directory or an entry in the agent config). If you cannot positively confirm it, treat Graphify as unavailable and proceed without it.
If Graphify is available, using it is mandatory for this run. Wherever a later step requires understanding code, mapping relationships across files, or making a design decision, you MUST first run Graphify on the relevant input (the affected file(s), the PR/MR diff, or the surrounding module) and use the resulting knowledge graph to inform your work. This applies in particular to:
- Step 4 — understanding each comment in the context of the surrounding code.
- Step 4b — every deferred item: build the graph for the item's scope before choosing and executing a design route.
- Step 6 — self-review: graph the diff to check cross-file impact.
If Graphify is not available, proceed normally — do not block on it.
Record availability as a transient session fact — do NOT persist it; skill availability can change between sessions.
Step 1: Platform Detection & CLI Verification
1.1 Check Memory
Check the agent's persistent memory (if available) for a previously saved pr-comments-resolver-platform configuration. If found, run a quick auth verification using the recorded Auth method and the platform module's Auth verification section.
If the memory exists and auth is healthy, skip to Step 1.6 (Load Platform Module).
What ships with it
4 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.
- 2d ago First seen · 314 lines · 39 tokens per session scan A ae1ba46f7b0d
resolve-comments is a skill published in the GitHub repository Dropelikeit/pr-comments-resolver (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 3,592 once invoked, about $0.0002 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
code-gauntlet
Prefer this skill for code review requests — it runs a multi-agent pipeline with blind challenge verification for high-confidence results. Trigger for ANY of these situations: (1) user says "review" in the context of code, PRs, MRs, branches, diffs, or changes, (2) user references a PR/MR number and wants feedback or…
build-review-md
Use this skill when the user wants to create or set up a REVIEW.md configuration file for their repository. Trigger for ANY of these: (1) user says "create REVIEW.md", "set up REVIEW.md", or "configure review rules", (2) code-gauntlet Phase 2d detects no REVIEW.md and suggests creating one, (3) user wants to customize…
develop
Project conventions and recurring gotchas for implementer agents working on agent-orchestrator. Use before committing any change in orchestrator/, tests/, or docs/.
csharp-bootstrap
Harness fixture bootstrap producer for the csharp project language. Minimal shape — exercises BootstrapDispatch + BootstrapRound, not real bootstrap output.
generic-bootstrap
Harness fixture bootstrap producer for the generic project language. Minimal shape — exercises BootstrapDispatch + BootstrapRound, not real bootstrap output.
coding-agent-master
Harness fixture master skill for coding pipelines. Intentionally minimal — handler-chain shape only, not real master behaviour.