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 jaybocc2/dotfiles --skill address-pr-feedbackgit clone --depth 1 https://github.com/jaybocc2/dotfilesWrote 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/jaybocc2/dotfiles/address-pr-feedback)<a href="https://agentmods.dev/skills/jaybocc2/dotfiles/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/jaybocc2/dotfiles/address-pr-feedback/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/jaybocc2/dotfiles/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/jaybocc2/dotfiles/address-pr-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00526 |
| Opus 5.5 | $0.00017 | $0.00210 |
| Sonnet 5.5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
address-pr-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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address PR Review Comments
Context
- Current branch: !
git branch --show-current - get pull request review with gh cli
Your task
Work through every unresolved review thread on this PR systematically. For each thread:
Step 1 — Understand the comment
Read the comment carefully. Identify:
- What file and line it refers to
- What the reviewer is asking for (change, question, clarification, nitpick)
- Whether a code change is actually required
Step 2 — Make changes if needed
If a code change is warranted:
- Read the relevant file(s) first
- Make the change using Edit (or Write for new files)
- Do NOT commit yet — collect all changes first
If no change is needed (e.g. the reviewer asked a question, or you disagree), prepare a clear explanation.
Step 3 — Commit each change separately
After addressing a comment that requires code changes, create a single follow-up commit. Write a short message that summarizes what was changed (e.g. "fix: use const for immutable bindings per review") rather than a generic message:
Skip this step if no code changes were made. Provide a commit message and wait until prompted to continue if not allowed by policy to commit.
Step 4 — Reply to each comment
use gh cli
Good reply patterns:
- For changes made: "Done — ."
- For questions answered: "< direct answer to question >."
- For declined suggestions: "I kept the existing approach because ."
- For issues already resolved in code: "I fixed this in "
Step 5 — Resolve each thread
Resolve every thread/comment if satisfactory use gh cli and GraphQL id field:
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "<thread_id>"}) { thread { id isResolved } } }'
Notes
- break down commits by units of work
- commits should be broken down into logical parts
- do not group unrelated changes into a single commit
- If the PR has no open review threads, report that there is nothing to address
- Always reply before resolving so the reviewer sees the response
- Keep replies concise and direct
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 · 62 lines · 42 tokens per session scan A 949174803884
address-pr-comments is a skill published in the GitHub repository jaybocc2/dotfiles (11 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 526 once invoked, about $0.0002 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-09-02.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
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.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
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.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.