ryanb/dotfiles is a collection of command-line configuration files for macOS, centered on Zsh and related tools such as Git, Ruby, Rails, and IRB. It is for developers who want to customize their terminal with commands, completions, prompts, and fuzzy-finding workflows. Its catalogue skills and plugin provide coding-agent workflows built into the same setup.
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 ryanb/dotfiles --skill pr-pending-feedbackgit clone --depth 1 https://github.com/ryanb/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/ryanb/dotfiles/pr-pending-feedback)<a href="https://agentmods.dev/skills/ryanb/dotfiles/pr-pending-feedback"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/pr-pending-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/ryanb/dotfiles/pr-pending-feedback"><img src="https://agentmods.dev/badge/skills/ryanb/dotfiles/pr-pending-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.00036 | $0.03622 |
| Opus 5.5 | $0.00014 | $0.01449 |
| Sonnet 5.5 | $0.00007 | $0.00724 |
| Haiku 4.5 | $0.00004 | $0.00362 |
Grade A, and why
pr-pending-feedback 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-pending-feedback — Triage and address pending PR review comments
The goal: look at every comment on the pending (unsubmitted) review the current user has drafted on the PR for the current branch, evaluate each one independently, split them into ones that can simply be addressed and ones that need discussion, work through the discussion comments one at a time, and — only after all discussions are resolved and the user confirms — dispatch a sub-agent per comment to fix it, one commit per comment.
These comments are the user's own. Never recommend skipping a comment. Every comment either gets addressed directly, or — if there's any ambiguity, subjectivity, design call, or doubt about applicability — gets opened up for discussion so the user can decide. "Skip" is only ever an outcome the user explicitly chooses during discussion, never something this skill proposes on its own.
Pending reviews are private to their author until submitted, so this skill only sees comments authored by the currently authenticated gh user.
Step 1: Find the PR for the current branch
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)
base_branch=$(gh pr view --json baseRefName --jq .baseRefName)
me=$(gh api user --jq .login)
If gh pr view fails, stop and tell the user there is no open PR for the current branch.
Step 2: Find the pending review
List reviews on the PR and find one in PENDING state authored by the current user:
gh api "repos/$repo/pulls/$pr_number/reviews" --jq \
".[] | select(.state==\"PENDING\" and .user.login==\"$me\") | {id, body, submitted_at, html_url}"
If there is no pending review, stop and tell the user there is no pending review on this PR for them. If there are multiple pending reviews (rare), list them and ask which to use.
Capture the id as review_id.
Step 3: Fetch the pending review's comments
gh api "repos/$repo/pulls/$pr_number/reviews/$review_id/comments"
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 · 208 lines · 36 tokens per session scan A a05877e42ce6
pr-pending-feedback is a skill published in the GitHub repository ryanb/dotfiles (2,400 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 3,622 once invoked, about $0.0001 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-30.
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.
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.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.