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 CiscoDevNet/essentials --skill pr-address-comments-allgit clone --depth 1 https://github.com/CiscoDevNet/essentialsWrote 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/ciscodevnet/essentials/pr-address-comments-all)<a href="https://agentmods.dev/skills/ciscodevnet/essentials/pr-address-comments-all"><img src="https://agentmods.dev/badge/skills/ciscodevnet/essentials/pr-address-comments-all.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.00169 | $0.03133 |
| Opus 5 | $0.00084 | $0.01566 |
| Sonnet 5 | $0.00034 | $0.00627 |
| Haiku 4.5 | $0.00017 | $0.00313 |
Grade B, and why
pr-address-comments-all scanned grade B with 1 finding 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 yesterday.
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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Script flags -> run any script with `--help`. How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Address Comments — All (parallel, one worktree per PR)
Address review comments across one or more GitHub PRs at the same time. Each PR is
isolated in its own git worktree checked out on the PR's branch, so work commits
locally and pushes straight back to the PR. This skill orchestrates the existing single-PR
procedure in pr-address-comments/SKILL.md — it does
not re-document its gh/GraphQL/commit steps; helper scripts and reference docs hold the
mechanics.
Quick start
You: address the review comments on my open PRs
You: fix my PRs that need changes
You: address the review comments on PRs 103 and 110
You: fix the comments on https://github.com/<owner>/<repo>/pull/103
You: address comments on PR 103, 110, 121 in parallel
Phases with one human checkpoint between analysis and code:
Phase 0 (auto) -> if no PR given, discover my open PRs that need attention (current repo)
Phase 1 (auto) -> look up each PR, create a worktree on its branch, fetch comments
Phase 2 (auto) -> draft a concrete fix-per-thread plan per PR (read-only)
GATE -> show the plans, wait for your approval
Phase 3 (auto) -> per PR: implement, commit, push to branch, reply + resolve threads
Phases 0–2 just start. Phase 3 never begins until you approve the plans, because a per-PR subagent may not understand the whole-repo context.
Inputs
- Zero or more PR references, each a full URL
(
https://github.com/<owner>/<repo>/pull/<N>) or a bare number (103). - Bare numbers resolve against the current repo's remote.
- With no reference, Phase 0 discovers your open PRs on the current repo's remote that have changes-requested or >=1 unresolved review comment.
Prerequisites
ghCLI authenticated with access to each PR's repository.- Inside a git repo;
git worktreeandopensslavailable. - Write access to each PR's branch for pushing (
git_write).
Limitations
- Same-repo PRs only. The workflow fetches and pushes the PR head branch through the
local repo's
originremote (git fetch origin -- <branch>/git push origin <branch>). Fork-based PRs — whose head branch lives in a fork or another remote — are not supported, becauseorigindoes not have that branch.
What ships with it
8 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.
- yesterday First seen · 241 lines · 169 tokens per session scan B 6fb76a3e039b
pr-address-comments-all is a skill published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 18d ago), licensed Apache-2.0. It adds 169 tokens to every session and 3,133 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
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.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
review_rebase
Queue a review then rebase combo for a PR (ex: /rr https://github.com/owner/repo/pull/42).
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.