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 emaraschio/cursor-commands --skill address-github-pr-commentsgit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/emaraschio/cursor-commands/address-github-pr-comments)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/address-github-pr-comments"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/address-github-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/emaraschio/cursor-commands/address-github-pr-comments"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/address-github-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.00015 | $0.00382 |
| Opus 5.5 | $0.00006 | $0.00153 |
| Sonnet 5.5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
address-github-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 1mo 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.
What it actually says
Overview
Process outstanding reviewer feedback, apply required fixes, and draft clear responses for each GitHub pull-request comment.
Steps
- Sync and audit comments
- Pull the latest branch changes
- Open the PR conversation view and read every unresolved comment
- Group comments by affected files or themes
- Plan resolutions
- List the requested code edits for each thread
- Identify clarifications or additional context you must provide
- Note any dependencies or blockers before implementing changes
- Implement fixes
- Apply targeted updates addressing one comment thread at a time
- Run relevant tests or linters after impactful changes
- Stage changes with commits that reference the addressed feedback
- Draft responses
- Summarize the action taken or reasoning provided for each comment
- Link to commits or lines when clarification helps reviewers verify
- Highlight any remaining questions or follow-up needs
Response Checklist
- All reviewer comments acknowledged
- Required code changes implemented and tested
- Clarifying explanations prepared for nuanced threads
- Follow-up items documented or escalated
- PR status updated for reviewers
Guardrails
- Push only when the user asks; do not push review fixes unrequested.
- Do not dismiss valid security feedback; address it or justify with evidence first.
- Address one comment thread at a time and run tests after impactful changes.
- Do not commit, push, merge, or run production scripts without consent; wait for an explicit request before any destructive git action.
- Do not print, log, or commit secrets or credentials; flag any exposed secret instead of including it in a commit or comment.
What ships with it
3 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.
- 1mo ago First seen · 44 lines · 15 tokens per session scan A eaef9153ce2a
address-github-pr-comments is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 18d ago), licensed MIT. It adds 15 tokens to every session and 382 once invoked, about $0.0001 per session on Opus 5.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
active-review
Use when the user wants to prepare for a manual PR code review and asks for help targeting it — a terse PR summary, ranked files to read first, and paste-ready inline comment drafts with GitHub deep-links. Triggers: "active review this PR", "walk me through this PR", "help me review this", "give me inline comments to…
pr-requirement-capture
Use when GH starts a message with "PR :" or "PR:". Treat the following text as a requirement that should be captured and worked through a GitHub pull-request workflow instead of remaining only in chat.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…