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 mitodl/agent-kit --skill address-pr-feedbackgit clone --depth 1 https://github.com/mitodl/agent-kitWrote 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/mitodl/agent-kit/address-pr-feedback)<a href="https://agentmods.dev/skills/mitodl/agent-kit/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/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/mitodl/agent-kit/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/address-pr-feedback.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.00218 | $0.07203 |
| Opus 5.5 | $0.00087 | $0.02881 |
| Sonnet 5.5 | $0.00044 | $0.01441 |
| Haiku 4.5 | $0.00022 | $0.00720 |
Grade A, and why
address-pr-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 yesterday.
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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address PR Feedback
Turns a PR's review activity — and its CI/status checks — into fixes plus a clean, fully-resolved thread list and a green check bar. The core pattern is fetch → categorize → address → reply & resolve → verify, using scripts for the mechanical parts so the interesting work is reading feedback correctly and knowing when a decision belongs to a human instead of you.
| Script | Purpose |
|---|---|
scripts/fetch-feedback.sh |
Fetch review threads (paginated), discussion comments, and reviews in one JSON payload |
scripts/fetch-checks.sh |
Fetch status checks (GitHub Actions + third-party) and failed-step logs for any failing Actions run |
scripts/resolve-thread.sh |
Reply to (optional) and resolve one review thread by GraphQL node ID |
scripts/resolve-threads.sh |
Batch version: reads [{"thread_id": "...", "comment": "..."}, ...] from stdin |
scripts/reply-comment.sh |
Post a top-level PR comment — for discussion-comment replies or a final summary |
See references/graphql-reference.md for
the underlying queries/mutations, why plain first: N GraphQL calls silently
truncate on long-running PRs, and why replying and resolving are separate
mutations. See references/checks-reference.md
for how the Checks API and third-party status checks differ, and how to
re-run or diagnose each.
Recognizing the request
The trigger is almost always a short imperative naming a PR, sometimes bundled with other git operations:
- "Address the PR feedback [on #N / <url>]"
- "For any comment that is addressed, mark it as resolved"
- "Address PR feedback, resolving comments that have been handled"
- "Rebase, resolve the conflicts, and then address the PR feedback"
- "Address feedback across the set of open PRs" / "walk through the PR chain, addressing feedback on the PRs first, then merge" (a stacked-PR batch)
- "Review the latest human-contributed feedback" / "there's more bot feedback to evaluate" (a re-check after previously addressing a first round)
- "Fix the failing checks [on #N]" / "the CI is red, why?" / "address the GitGuardian alert" / "prek is failing" / "pre-commit.ci is failing" — a checks-only request, not review-comment feedback; jump straight to Phase 1b — Checks below
- "Address the PR feedback" alone, with no mention of checks, still means glance at the check bar (Phase 1b) — a PR with unresolved review comments and a failing required check is not addressed until both are handled
What ships with it
8 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.
- evals/evals.json 2.8 KB
- references/checks-reference.md 4.9 KB
- references/graphql-reference.md 5.5 KB
- scripts/fetch-checks.sh 2.5 KB runs code
- scripts/fetch-feedback.sh 5.3 KB runs code
- scripts/reply-comment.sh 1.1 KB runs code
- scripts/resolve-thread.sh 2.2 KB runs code
- scripts/resolve-threads.sh 1.2 KB runs code
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.
- yesterday Changed · +125 lines · -3 tokens per session e64b44a70df5
- 8d ago Changed · +18 lines 614e8f63f822
- 15d ago Changed 8e99e53392f0
- 16d ago Changed · +15 lines · +23 tokens per session eab89c015663
- 1mo ago First seen · 392 lines · 198 tokens per session scan A 8d78396935d7
address-pr-feedback is a skill published in the GitHub repository mitodl/agent-kit (5 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 218 tokens to every session and 7,203 once invoked, about $0.0009 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
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.
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.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…