Latitude is an open-source platform for monitoring AI agents by collecting execution traces, grouping failures, dispatching coding agents to make fixes, and replaying failures to verify them. Teams use it to observe agent behavior, investigate errors, and monitor whether fixes prevent regressions. The catalogue entries include skills, instructions, and an MCP server for working with Latitude.
Borrowing it
Nothing to install: this file belongs to latitude-dev/latitude-llm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/latitude-dev/latitude-llm/development/.agents/skills/review-pr-comments/SKILL.mdgit clone --depth 1 https://github.com/latitude-dev/latitude-llmWrote 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/latitude-dev/latitude-llm/review-pr-comments)<a href="https://agentmods.dev/skills/latitude-dev/latitude-llm/review-pr-comments"><img src="https://agentmods.dev/badge/skills/latitude-dev/latitude-llm/review-pr-comments/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/skills/latitude-dev/latitude-llm/review-pr-comments"><img src="https://agentmods.dev/badge/skills/latitude-dev/latitude-llm/review-pr-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.02687 |
| Opus 5 | $0.00037 | $0.01344 |
| Sonnet 5 | $0.00015 | $0.00537 |
| Haiku 4.5 | $0.00007 | $0.00269 |
Grade A, and why
review-pr-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 9d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR comments: sequential review workflow
Walk the current PR’s feedback in order, one topic at a time. Treat each comment as something to read and answer; treat each underlying issue as something to fix once. If several comments say the same thing (or the first fix already covers a later remark), do not redo the same code work—use one commit for that shared fix and reply on each later comment pointing at that commit (e.g. “Addressed in <sha> — same fix as …”).
Prerequisites
ghauthenticated (gh auth status).- A PR for the checked-out branch (
gh pr viewwithout a number targets it). - Follow repo rules for git write: do not commit or push unless authorized for this session.
Pick the best gh command per step
gh pr …, gh api (REST), and gh api graphql hit different GitHub APIs—same intent, not interchangeable. There is no blanket rule favoring one surface; choose whatever is correct and clearest for that action.
| Step | Typically strongest option | Why |
|---|---|---|
| Quick PR metadata | gh pr view --json number,url,title,… |
Native fields, branch defaults |
| Readable timeline + review summaries | gh pr view --comments |
Human-readable; good scan |
| Structured issue comments / review objects | gh pr view --json comments,reviews,latestReviews |
Easy JSON for sorting |
| Inline comments plus threads, resolve state | gh api graphql (reviewThreads) |
Threads + isResolved + thread.id for mutations |
| Flat list of inline comments only | gh api repos/{owner}/{repo}/pulls/<n>/comments --paginate |
Simple; reply ids (id) for REST replies |
| Post a conversation comment | gh pr comment |
Correct for timeline |
| Reply under a line comment | gh api -X POST …/pulls/<n>/comments/<id>/replies |
gh pr comment does not thread on the diff |
| Resolve a review thread | gh api graphql (resolveReviewThread) |
Only API that exposes it |
| Inspect the patch | gh pr diff |
First-class diff |
| Need UI context (complex thread) | gh pr view --web |
When it helps—no ban |
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.
- 9d ago First seen · 224 lines · 74 tokens per session scan A 862b0d132ffb
review-pr-comments is a skill published in the GitHub repository latitude-dev/latitude-llm (4,632 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 2,687 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-30.
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.