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 Muriel-Salvan/x_aeon_agents --skill addressing-pull-request-commentsgit clone --depth 1 https://github.com/Muriel-Salvan/x_aeon_agentsWrote 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/muriel-salvan/x_aeon_agents/addressing-pull-request-comments)<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/addressing-pull-request-comments"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/addressing-pull-request-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/muriel-salvan/x_aeon_agents/addressing-pull-request-comments"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/addressing-pull-request-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.00085 | $0.01700 |
| Opus 5.5 | $0.00034 | $0.00680 |
| Sonnet 5.5 | $0.00017 | $0.00340 |
| Haiku 4.5 | $0.00009 | $0.00170 |
Grade A, and why
addressing-pull-request-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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Addressing Pull Request comments
Sequential steps to be followed when using this skill
When addressing Pull Request comments, follow those steps.
Create the addressing-pull-request-comments Execution Checklist (MANDATORY)
- Before executing anything, create a checklist named addressing-pull-request-comments Execution Checklist with all steps of these instructions.
- The addressing-pull-request-comments Execution Checklist must include all numbered steps explicitly.
- After completing each step of these instructions, mark the item in the addressing-pull-request-comments Execution Checklist as completed.
- Do not skip any item.
- If an item cannot be executed, explicitly explain why.
- Never mark the task as completed while any item from the addressing-pull-request-comments Execution Checklist remains open.
1. Inform the user
- Always tell the user "SKILL: I am addressing Pull Request comments" to inform the user that you are running this skill.
2. Fetch Pull Request comments (can be done during Plan mode)
- Find this skill directory path, later referenced as {skill_path}.
- Always use
cli: ruby {skill_path}/scripts/check_unresolved_pr_commentsto know about all the unresolved PR comments.
Example with expected output as JSON:
ruby .cline/skills/addressing-pull-request-comments/scripts/check_unresolved_pr_comments
# => Repository Github handle: Muriel-Salvan/ruby-neural-nets
# Branch name: main
# Found 1 Pull Requests dealing with this branch (numbers 3)
# Unresolved review threads and comments found on Pull Request #3:
# {
# "data": {
# "repository": {
# "pullRequest": {
# "url": "https://github.com/Muriel-Salvan/ruby-neural-nets/pull/3",
# "reviewDecision": null,
# "reviewThreads": {
# "edges": [
# {
# "node": {
# "isResolved": false,
# "comments": {
# "totalCount": 1,
# "nodes": [
# {
# "databaseId": 2718057900,
# [...]
# "body": "Tests are failing. Please check again and fix it.",
# "subjectType": "LINE",
# "path": "lib/ruby_neural_nets/datasets/file_to_image_magick.rb",
# "commit": {
# "oid": "9ca8a54eccded4df1ea32520a05bce6f8bc665dd",
# "message": "Silence ffmpeg output by monkey-patching Open3.capture3 and Kernel.system to intercept and silence ffmpeg commands"
# },
# }
# ]
# }
# }
# }
# ]
# }
# }
# }
# }
# }
Example of an error case with a non-existing Pull Request:
ruby .cline/skills/addressing-pull-request-comments/scripts/check_unresolved_pr_comments
# => Repository Github handle: Muriel-Salvan/x_aeon_agents
# Branch name: main
# Found 0 Pull Requests dealing with this branch (numbers )
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 169 lines · 85 tokens per session scan A 5ad38c5d6f40
addressing-pull-request-comments is a skill published in the GitHub repository Muriel-Salvan/x_aeon_agents (2 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 85 tokens to every session and 1,700 once invoked, about $0.0003 per session on Opus 5.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
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…