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 ggg123124/vrchat-assistant --skill address-github-commentsgit clone --depth 1 https://github.com/ggg123124/vrchat-assistantWrote 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/ggg123124/vrchat-assistant/address-github-comments)<a href="https://agentmods.dev/skills/ggg123124/vrchat-assistant/address-github-comments"><img src="https://agentmods.dev/badge/skills/ggg123124/vrchat-assistant/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/ggg123124/vrchat-assistant/address-github-comments"><img src="https://agentmods.dev/badge/skills/ggg123124/vrchat-assistant/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.00339 |
| Opus 5.5 | $0.00011 | $0.00136 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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 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.
This is a copy
86% identical to address-github-comments — 28 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.
What it actually says
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
Or use a custom script if available to list threads.
2. Categorize and Plan
- List the comments and review threads.
- Propose a fix for each.
- Wait for user confirmation on which comments to address first if there are many.
3. Apply Fixes
Apply the code changes for the selected comments.
4. Respond to Comments
Once fixed, respond to the threads as resolved.
gh pr comment <PR_NUMBER> --body "Addressed in latest commit."
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
This skill is applicable to execute the workflow or actions described in the overview.
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 · 65 lines · 27 tokens per session scan A ec96b2cc76ec
address-github-comments is a skill published in the GitHub repository ggg123124/vrchat-assistant (26 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to address-github-comments, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
github-profile-readme
Build or rewrite a GitHub profile README (the username/username special repo) with a personalized theme — animated SVG banner, stats cards, contribution snake, tech badges, project/research tables. Includes the git conflict pitfall when the local clone is stale vs GitHub web edits, and the PyYAML on: quirk for…
github-code-review
Review PRs: diffs, inline comments via gh or REST.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
orbit-github
Open Orbit briefing skill — selected by the Orbit pipeline when GitHub is the user's only connected connector, or when the user explicitly scopes their daily digest to GitHub. Pulls the past 24 hours of PRs, review requests, issues, CI runs, and merges from the user's authenticated GitHub connection and renders them…
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
pr
Create a pull request using the Dedalus PR template. Injects git state, commit history, and diff stats automatically.