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.
git 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/commands/emaraschio/cursor-commands/address-github-pr-comments)<a href="https://agentmods.dev/commands/emaraschio/cursor-commands/address-github-pr-comments"><img src="https://agentmods.dev/badge/commands/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/commands/emaraschio/cursor-commands/address-github-pr-comments"><img src="https://agentmods.dev/badge/commands/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.00395 |
| Opus 5.5 | $0.00006 | $0.00158 |
| Sonnet 5.5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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
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
- Read
.cursor/skill-contracts/address-github-pr-comments/SKILL.mdfor the full agent contract; if that file is missing, read~/.cursor/skill-contracts/address-github-pr-comments/SKILL.md. - Execute the workflow in order; do not skip safety steps.
- 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.
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 · 38 lines · 15 tokens per session scan A ae805e051ebb
address-github-pr-comments is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 15d ago), licensed MIT. It adds 15 tokens to every session and 395 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 commands, from other repositories
resolve_pr_parallel
Resolve all PR comments using parallel processing.
pr-reviewer
Review a Git branch as a PR against the base branch (auto-resolved — main/master) judged by THIS repo's contract (CLAUDE.md + .claude/skills/). Three-dot diff, route changed paths to skills, verify (eslint/prettier/tsc + tests), tiered report + confidence. Optional gated fix + commit after the report.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
gss-pr
Create a feature branch and open a pull request via gss pr.
pr-review
Intelligent PR code review with dynamic agent allocation based on change types.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.