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 lttr/claude-marketplace --skill pr-commentsgit clone --depth 1 https://github.com/lttr/claude-marketplaceWrote 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/lttr/claude-marketplace/pr-comments)<a href="https://agentmods.dev/skills/lttr/claude-marketplace/pr-comments"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/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/lttr/claude-marketplace/pr-comments"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/pr-comments.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.00070 | $0.01068 |
| Opus 5 | $0.00035 | $0.00534 |
| Sonnet 5 | $0.00014 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
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 10d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Comments (Azure DevOps)
Read, assess, and post code-level comments on Azure DevOps pull requests.
API Reference
The az repos pr CLI does not support PR threads. Use az devops invoke for all thread operations.
Detect project and repositoryId from git remote or az devops configure --list.
Fetch all threads
az devops invoke \
--area git \
--resource pullRequestThreads \
--route-parameters \
project=<project> \
repositoryId=<repo-name-or-id> \
pullRequestId=<pr-id> \
-o json
Create thread on file/line
az devops invoke \
--area git \
--resource pullRequestThreads \
--route-parameters \
project=<project> \
repositoryId=<repo-name-or-id> \
pullRequestId=<pr-id> \
--http-method POST \
--in-file <(cat <<'EOF'
{
"comments": [
{
"parentCommentId": 0,
"content": "Comment text (markdown supported)",
"commentType": 1
}
],
"threadContext": {
"filePath": "/path/to/file.vue",
"rightFileStart": { "line": 31, "offset": 1 },
"rightFileEnd": { "line": 38, "offset": 1 }
},
"status": 1
}
EOF
)
Thread status: 0 = unknown, 1 = active, 2 = fixed, 3 = won't fix, 4 = closed, 5 = by design, 6 = pending
Line targeting:
rightFileStart/rightFileEnd- new code (most common)leftFileStart/leftFileEnd- deleted code- Single line: same start and end
- Omit
threadContextentirely for a general (non-file) comment
Reply to existing thread
az devops invoke \
--area git \
--resource pullRequestThreadComments \
--route-parameters \
project=<project> \
repositoryId=<repo-name-or-id> \
pullRequestId=<pr-id> \
threadId=<thread-id> \
--http-method POST \
--in-file <(cat <<'EOF'
{"content": "Reply text"}
EOF
)
Verify success: Response contains "id": field. Do NOT retry if first attempt returns valid JSON with an ID.
Posting: Comment Text Style
When posting review comments to PRs, be concise:
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.
- 10d ago First seen · 152 lines · 70 tokens per session scan A 80775dbfbffd
pr-comments is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 1,068 once invoked, about $0.0003 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
verify-change
A change-checking skill that reviews code differences and checks whether related documentation, tests, and records were updated.
verify-module
A module-checking skill that scans a project’s folders, code, and documentation. It expects each module to include a README.md and DESIGN.md, which explain how the module is used and why it was designed that way.
verify-quality
A code-quality checker that measures complexity, size, naming, and common code smells. It reports problems such as duplicated code, unused code, and overly long functions.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.