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/djrhails/dotfiles/pr-commentsnpx skills add DJRHails/dotfiles --skill pr-commentsgit clone --depth 1 https://github.com/DJRHails/dotfilesWhat 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.00039 | $0.01226 |
| Opus 5 | $0.00019 | $0.00613 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
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 2d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Comments
Fetch and address review comments on the PR for the current branch.
Prerequisites
ghCLI authenticated- Current branch has an open PR
Step 1: Identify the PR
BRANCH=$(git branch --show-current)
Guard: skip if branch is main or master.
PR_NUM=$(gh pr view --json number -q .number)
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
OWNER=$(echo $REPO | cut -d/ -f1)
REPO_NAME=$(echo $REPO | cut -d/ -f2)
If no PR found, inform the user and stop.
Step 2: Fetch review data
Run these in parallel:
# Inline code review comments (threaded)
gh api "repos/$REPO/pulls/$PR_NUM/comments" --paginate \
--jq '.[] | {id, path, line, body, user: .user.login, created_at, in_reply_to_id, diff_hunk}'
# Top-level reviews (approval / request-changes + body)
gh api "repos/$REPO/pulls/$PR_NUM/reviews" --paginate \
--jq '.[] | {id, user: .user.login, state, body}'
# General PR discussion comments
gh api "repos/$REPO/issues/$PR_NUM/comments" --paginate \
--jq '.[] | {id, user: .user.login, body, created_at}'
Step 3: Group into threads
- A comment with
in_reply_to_id: nullstarts a thread. - Replies link to their parent via
in_reply_to_id. - Track: file, line, diff hunk, author, all replies in order.
Step 4: Classify
Bot comments (login ends with [bot]): summarise briefly, only surface actionable failures.
Human comments: full treatment in Step 5.
Step 5: For each unresolved human comment
- Show context: file, line, diff hunk, comment body.
- Read the current file at the referenced location.
- Summarise the reviewer's concern in one sentence.
- Assess: Is the feedback valid? Use your judgement — reviewers may lack context or be wrong.
- Propose a concrete action and ask the user:
- Fix → apply the code change (do NOT commit)
- Reply → post a reply via
gh api - Skip → move on
For already-resolved threads, present as a summary group and ask if user wants to revisit.
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.
- 2d ago First seen · 147 lines · 39 tokens per session scan A 3db5e52f4b4a
pr-comments is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 1,226 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
autopilot-batch
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
qa-handoff
Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
dustoff
Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current conventions — delegating every fix to the skill that owns it, and optionally capturing the plan as a tracking issue that survives…