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 yeaight7/agent-powerups --skill gh-address-commentsgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/gh-address-comments)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/gh-address-comments"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/gh-address-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/yeaight7/agent-powerups/gh-address-comments"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/gh-address-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.00040 | $0.00890 |
| Opus 5.5 | $0.00016 | $0.00356 |
| Sonnet 5.5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
gh-address-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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR Comment Handler
Use this skill when the user wants to work through requested changes on a GitHub pull request. Use the GitHub MCP or gh CLI for PR metadata and patch context. Treat thread-aware review data as a gh api graphql problem — the flat comment surface does not preserve full review-thread state.
Run all gh commands with elevated network access. If CLI auth is required, confirm gh auth status first and ask the user to authenticate with gh auth login if it fails.
Workflow
-
Resolve the PR.
- If the user provides a repository and PR number or URL, use that directly.
- If the request is about the current branch PR, use local git context:
gh pr view --json number,url.
-
Inspect review context with thread-aware reads.
- Use
gh api graphqlwhenever the task depends on unresolved review threads, inline review locations, or resolution state — it fetchesreviewThreads,isResolved,isOutdated, and file/line anchors. - Use flat comment reads only for lightweight top-level PR comment summaries.
- Use
-
Cluster actionable review threads.
- Group comments by file or behavior area.
- Separate actionable change requests from informational comments, approvals, already-resolved threads, and duplicates.
-
Confirm scope before editing.
- Present numbered actionable threads with a one-line summary of the required change.
- If the user did not ask to fix everything, ask which threads to address.
- If the user asks to fix everything, interpret that as all unresolved actionable threads and call out anything ambiguous.
-
Implement the selected fixes locally.
- Keep each code change traceable back to the thread or feedback cluster it addresses.
- If a comment calls for explanation rather than code, draft the response rather than forcing a code change.
-
Summarize the result.
- List which threads were addressed, which were intentionally left open, and what tests or checks support the change.
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 · 87 lines · 40 tokens per session scan A 0a8c429ff004
gh-address-comments is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 16d ago), licensed Apache-2.0. It adds 40 tokens to every session and 890 once invoked, about $0.0002 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-09-14.
Other skills, from other repositories
github-code-review
Review PRs: diffs, inline comments via gh or REST.
simplify-code
Sequential 3-lens cleanup of recent code changes.
requesting-code-review
Pre-commit review: security scan, quality gates, auto-fix.
github-auth
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI.
github-repo-management
Clone, create, fork repos; manage remotes, releases.
aidd-pr
Triage PR review comments, resolve already-addressed threads, and delegate /aidd-fix prompts for remaining issues. Use when a PR has open review comments that need to be triaged, resolved, or delegated to sub-agents.