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 skills/doidor/agentrig/address-review-commentsnpx skills add doidor/agentrig --skill address-review-commentsgit clone --depth 1 https://github.com/doidor/agentrigWrote 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/doidor/agentrig/address-review-comments)<a href="https://agentmods.dev/skills/doidor/agentrig/address-review-comments"><img src="https://agentmods.dev/badge/skills/doidor/agentrig/address-review-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.00030 | $0.00397 |
| Opus 5 | $0.00015 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
address-review-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 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.
What it actually says
address-review-comments (principles 4, 5)
Read the PR feedback and address each requested change. Mark each addressed thread resolved so the review watcher can see feedback was handled. You are repairing, not re-reviewing — preserve the PR's original scope.
Steps
- List unresolved feedback — every active review thread, plus any PR-level "request
changes" review body (those can block merge without a resolvable thread; treat them as required
feedback too). Use the repo's forge CLI/API (e.g.
gh pr view/gh apifor GitHub). - For each thread: if valid, make the fix, commit, push; if you disagree, reply explaining why.
- Reply on every thread before resolving it, one short line stating what was done:
Fixed in <sha>: <summary>·Won't fix: <reason>·Already addressed in <sha>: <pointer>. The per-thread audit trail is what builds reviewer confidence — don't substitute a single summary comment.
- Resolve every thread you replied to. Many repos gate merge on "conversation resolution", so a replied-but-unresolved thread still blocks.
- Verify zero active threads remain before declaring done, and confirm every PR-level changes-requested review was addressed or explicitly rejected, fixes committed and pushed.
- Run
self-verifybefore handoff.
Repair-mode rules
- Do not bounce the task back without evidence: fix, reply, resolve, push.
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 · 33 lines · 30 tokens per session scan A 19211dcf6fbd
address-review-comments is a skill published in the GitHub repository doidor/agentrig (5 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 397 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…