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 ahmadharis/agentskills --skill azure-pr-commentsgit clone --depth 1 https://github.com/ahmadharis/agentskillsWrote 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/ahmadharis/agentskills/azure-pr-comments)<a href="https://agentmods.dev/skills/ahmadharis/agentskills/azure-pr-comments"><img src="https://agentmods.dev/badge/skills/ahmadharis/agentskills/azure-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/ahmadharis/agentskills/azure-pr-comments"><img src="https://agentmods.dev/badge/skills/ahmadharis/agentskills/azure-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.00075 | $0.03010 |
| Opus 5 | $0.00037 | $0.01505 |
| Sonnet 5 | $0.00015 | $0.00602 |
| Haiku 4.5 | $0.00007 | $0.00301 |
Grade D, and why
azure-pr-comments scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Linux**: `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- **Linux**: `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Linux**: `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` How it starts
The opening of the file, as written. The whole thing — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps PR Comments
List, add, reply to, resolve, and delete comment threads on Azure DevOps pull requests.
Invocation
| Mode | Command | Behavior |
|---|---|---|
| List | /azure-pr-comments |
List threads on current branch's PR |
| List | /azure-pr-comments <pr-id> |
List threads on specified PR |
| Add | /azure-pr-comments add |
Add a comment to current PR |
| Reply | /azure-pr-comments reply |
Reply to a thread |
| Resolve | /azure-pr-comments resolve |
Resolve/close a thread |
The LLM determines the PR ID, thread ID, and content from context. Natural language also works:
- "What comments are on my PR?"
- "Add a comment to PR 123: looks good"
- "Reply to thread 5 on PR 123: fixed in latest commit"
- "Resolve all threads on my PR"
- "Mark thread 5 as won't fix"
Prerequisites
Verify az CLI is available before proceeding. Run:
az --version
If the command fails, inform the user how to install it:
- macOS:
brew install azure-cli - Windows:
winget install --exact --id Microsoft.AzureCLI - Linux:
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
Windows shell requirement: All commands in this skill use bash syntax (sed, mktemp, jq, etc.). On Windows, run in Git Bash or WSL — PowerShell and cmd are not supported.
Then ensure the Azure DevOps extension is installed:
az extension add --name azure-devops
Detect Repository Info
Extract organization, project, and repository from the git remote:
REMOTE_URL=$(git remote get-url origin)
ORG=$(echo "$REMOTE_URL" | sed -n 's|.*dev.azure.com/\([^/]*\)/.*|\1|p')
PROJECT=$(echo "$REMOTE_URL" | sed -n 's|.*dev.azure.com/[^/]*/\([^/]*\)/.*|\1|p')
REPO=$(echo "$REMOTE_URL" | sed -n 's|.*/_git/\(.*\)|\1|p')
Then get the repository ID (required by the threads API):
REPO_ID=$(az repos show --repository "$REPO" --org "https://dev.azure.com/$ORG" --project "$PROJECT" --query "id" -o tsv)
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.
- 9d ago First seen · 394 lines · 75 tokens per session scan D a5eac213931f
azure-pr-comments is a skill published in the GitHub repository ahmadharis/agentskills (2 stars, last pushed 5mo ago), licensed MIT. It adds 75 tokens to every session and 3,010 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.