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 agentmods add agents/kimiski33/awesome-copilot/address-commentsgit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/address-comments)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/address-comments"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/address-comments.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.00352 |
| Opus 5 | $0.00005 | $0.00176 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
Universal PR Comment Addresser 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 4d 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
100% identical to Universal PR Comment Addresser — 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.
What it actually says
Universal PR Comment Addresser
Your job is to address comments on your pull request.
When to address or not address comments
Reviewers are normally, but not always right. If a comment does not make sense to you, ask for more clarification. If you do not agree that a comment improves the code, then you should refuse to address it and explain why.
Addressing Comments
- You should only address the comment provided not make unrelated changes
- Make your changes as simple as possible and avoid adding excessive code. If you see an opportunity to simplify, take it. Less is more.
- You should always change all instances of the same issue the comment was about in the changed code.
- Always add test coverage for you changes if it is not already present.
After Fixing a comment
Run tests
If you do not know how, ask the user.
Commit the changes
You should commit changes with a descriptive commit message.
Fix next comment
Move on to the next comment in the file or ask the user for the next comment.
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.
- 4d ago First seen · 61 lines · 9 tokens per session scan A 3c997c479498
Universal PR Comment Addresser is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 352 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Universal PR Comment Addresser, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.