agentmods.dev

address-github-pr-comments

A command for addressing review comments on the current GitHub pull request, a proposed code change under review. It follows a defined workflow and includes safety rules for security feedback and pushing changes.

In plain words
What is it for?
Use it to inspect pull-request comments, make the requested fixes, report the outcomes, and push changes only when explicitly asked.
Why use it?
It organizes responses to reviewer requests while reducing the risk of dismissing valid concerns or notifying reviewers with unfinished changes.

Command for Cursor

9 26d ago A scan 15 tokens original MIT
View the source file emaraschio/cursor-commands
Install

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.

agentmods
npx agentmods add commands/emaraschio/cursor-commands/address-github-pr-comments
Clone the repo
git clone --depth 1 https://github.com/emaraschio/cursor-commands

Made for: Cursor.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 395 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00395
Opus 5 $0.00008 $0.00198
Sonnet 5 $0.00003 $0.00079
Haiku 4.5 $0.00002 $0.00040

Measured 2d ago against content hash ae805e051ebb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.cursor/commands/address-github-pr-comments.md · 38 lines

What it actually says

Overview

Address review comments on the current GitHub PR. Full workflow: .cursor/skill-contracts/address-github-pr-comments/SKILL.md (user install: ~/.cursor/skill-contracts/address-github-pr-comments/SKILL.md).

Defaults

None. See skill for workflow defaults.

Steps

  1. Read .cursor/skill-contracts/address-github-pr-comments/SKILL.md for the full agent contract; if that file is missing, read ~/.cursor/skill-contracts/address-github-pr-comments/SKILL.md.
  2. Execute the workflow in order; do not skip safety steps.
  3. Report outcomes per skill (summary, tables, or checklist as specified).

Anti-patterns

  • Push only when asked. Trigger: fixes for review comments are committed. Wrong: pushing to the PR branch without being asked. Correct: push only on an explicit request from the user. Reason: an unrequested push can trigger CI and notify reviewers before the work is ready.
  • Do not dismiss valid security feedback. Trigger: a reviewer raises a security concern. Wrong: marking the thread resolved without addressing it. Correct: address the concern or justify with evidence before resolving. Reason: dismissing valid security feedback can ship a real vulnerability.

Examples

  • /address-github-pr-comments

Maintainers

Behavioral eval: .cursor/skill-contracts/address-github-pr-comments/eval/cases.md. Ship gate sections: A, S before changing SKILL.md or this command.

Changes

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.

  1. 2d ago First seen · 38 lines · 15 tokens per session scan A ae805e051ebb

Subscribe to this mod's changes

address-github-pr-comments is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 26d ago), licensed MIT. It adds 15 tokens to every session and 395 once invoked, about $0.0001 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.

Code reviewGit and workflowagent-skillsai-agentscursorcursor-idedeveloper-toolsdotfiles
Related

Other commands, from other repositories

grok_execute

Explicitly turn the task-local Grok executor mode on or off.

Vanyangyang/cursor-bridge · 14 tokens

thirdparty-web-interface-guidelines

Review these files for compliance: $ARGUMENTS.

kensaurus/cursor-kenji · 15 tokens

plan

Research, clarify requirements, and produce an approved implementation plan before writing code (Cursor Plan Mode).

kensaurus/cursor-kenji · 19 tokens

green-repo

Drive the whole repository to a verified-green baseline — typecheck, lint, tests, build — with authorized fixing of pre-existing debt.

kensaurus/cursor-kenji · 26 tokens

ship-and-observe

Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.

kensaurus/cursor-kenji · 31 tokens

gate-logic

Audit CI/CD gate logic — silent bypass, ratchet gaming, conflicting conditions — report only.

kensaurus/cursor-kenji · 18 tokens