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/mitodl/agent-kit/address-pr-feedbacknpx skills add mitodl/agent-kit --skill address-pr-feedbackgit clone --depth 1 https://github.com/mitodl/agent-kitWhat 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.00198 | $0.05092 |
| Opus 5 | $0.00099 | $0.02546 |
| Sonnet 5 | $0.00040 | $0.01018 |
| Haiku 4.5 | $0.00020 | $0.00509 |
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 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 — 392 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" / "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
7 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.
- 2d 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 (2 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 198 tokens to every session and 5,092 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…