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 iradoweck/antigravity-awesome-skills --skill address-github-commentsgit clone --depth 1 https://github.com/iradoweck/antigravity-awesome-skillsWrote 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/iradoweck/antigravity-awesome-skills/address-github-comments)<a href="https://agentmods.dev/skills/iradoweck/antigravity-awesome-skills/address-github-comments"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/address-github-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/iradoweck/antigravity-awesome-skills/address-github-comments"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/address-github-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.00027 | $0.00541 |
| Opus 5.5 | $0.00011 | $0.00216 |
| Sonnet 5.5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
address-github-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 11d 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.
This is a copy
98% identical to address-github-comments — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address GitHub Comments
Overview
Efficiently address PR review comments or issue feedback using the GitHub CLI (gh). This skill ensures all feedback is addressed systematically.
Prerequisites
Ensure gh is authenticated.
gh auth status
If not logged in, run gh auth login.
Workflow
1. Inspect Comments
Fetch the comments for the current branch's PR.
gh pr view --comments
--comments shows conversation comments; it does not enumerate every inline review thread.
Use the available GitHub connector or the GraphQL pullRequest.reviewThreads connection
with pagination to inspect inline comments, file/line anchors, and resolution state.
Record the repository, PR number, current head SHA, thread IDs, and requested changes.
2. Categorize and Plan
- List the comments and review threads.
- Propose a fix for each.
- Address feedback already covered by the user's requested scope. Ask only when feedback conflicts, expands scope, or requires a consequential choice.
3. Apply Fixes
Read the surrounding implementation, preserve unrelated edits, and apply the changes for the selected comments. Run the relevant repository checks and bind the result to the updated head before reporting a fix.
4. Respond to Comments
When the user authorizes posting replies, respond with the commit and verification evidence. A conversation comment does not resolve an inline review thread. Resolve the specific thread through the supported GitHub API only after its request is actually addressed and resolution is authorized; otherwise leave a proposed reply for the user.
gh pr comment <PR_NUMBER> --body "Addressed in <commit SHA>; verified with <check and result>."
Common Mistakes
- Applying fixes without understanding context: Always read the surrounding code of a comment.
- Not verifying auth: Check
gh auth statusbefore starting.
When to Use
Use when an existing PR has review threads or issue comments that require a scoped code repair and an evidence-backed response.
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.
- 11d ago Changed · +6 lines 1ee3ffe2a310
- 1mo ago Changed 1b14e16c2663
- 1mo ago First seen · 67 lines · 27 tokens per session scan A 463a2a0f2720
address-github-comments is a skill published in the GitHub repository iradoweck/antigravity-awesome-skills (30 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 541 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to address-github-comments, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…