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 Ghosteken/agent-harness --skill address-github-commentsgit clone --depth 1 https://github.com/Ghosteken/agent-harnessWrote 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/ghosteken/agent-harness/address-github-comments)<a href="https://agentmods.dev/skills/ghosteken/agent-harness/address-github-comments"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/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/ghosteken/agent-harness/address-github-comments"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/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.00381 |
| Opus 5.5 | $0.00011 | $0.00152 |
| Sonnet 5.5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
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
98% identical to address-github-comments — 20 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.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
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 · 67 lines · 27 tokens per session scan A 463a2a0f2720
address-github-comments is a skill published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 381 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 20 lines, and is treated as a copy.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
github
Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
review-open-pull-requests
List and analyze all open pull requests across GitHub repositories. Shows review status, CI/CD check results, age, and reviewers. Use when triaging PRs, checking team velocity, or identifying stale reviews that need attention.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.