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 felipeelias/claude-marketplace --skill address-commentsgit clone --depth 1 https://github.com/felipeelias/claude-marketplaceWrote 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/felipeelias/claude-marketplace/address-comments)<a href="https://agentmods.dev/skills/felipeelias/claude-marketplace/address-comments"><img src="https://agentmods.dev/badge/skills/felipeelias/claude-marketplace/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/felipeelias/claude-marketplace/address-comments"><img src="https://agentmods.dev/badge/skills/felipeelias/claude-marketplace/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.00034 | $0.00504 |
| Opus 5 | $0.00017 | $0.00252 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
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 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.
What it actually says
Context
- PR number: !
gh pr view --json number --jq .number - PR URL: !
gh pr view --json url --jq .url - Repo: !
gh repo view --json nameWithOwner --jq .nameWithOwner - Branch: !
git branch --show-current
Steps
1. Fetch all comments
Run in parallel, using the repo and PR number from context:
gh api repos/{REPO}/pulls/{PR}/comments— inline review commentsgh api repos/{REPO}/pulls/{PR}/reviews— review bodies (contain nitpicks and summaries)
2. Categorize and present
Show the user a table:
| # | Source | File | Status | Issue |
|---|
Statuses: Already fixed, Actionable, Skip (with reason).
Wait for user confirmation before proceeding.
3. Fix actionable items
Read each file, make the fix, verify it addresses the comment.
4. Validate, commit, push
Run the project's linter and tests before committing. Commit with fix: address review feedback (...). Push to the PR branch.
5. Reply and resolve threads
For each addressed thread, reply with a short comment explaining what was fixed and in which commit, then resolve the thread.
# Reply to inline comment
gh api repos/{REPO}/pulls/{PR}/comments/{COMMENT_ID}/replies -f body='Fixed in {SHA} — {what was done}.'
# Resolve the thread
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "ID"}) { thread { isResolved } } }'
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 First seen · 54 lines · 34 tokens per session scan A 2f1528abe91e
address-comments is a skill published in the GitHub repository felipeelias/claude-marketplace (1 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 504 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).