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/existential-birds/beagle/fetch-pr-feedbacknpx skills add existential-birds/beagle --skill fetch-pr-feedbackgit clone --depth 1 https://github.com/existential-birds/beagleWrote 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/existential-birds/beagle/fetch-pr-feedback)<a href="https://agentmods.dev/skills/existential-birds/beagle/fetch-pr-feedback"><img src="https://agentmods.dev/badge/skills/existential-birds/beagle/fetch-pr-feedback.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.02684 |
| Opus 5 | $0.00009 | $0.01342 |
| Sonnet 5 | $0.00003 | $0.00537 |
| Haiku 4.5 | $0.00002 | $0.00268 |
Grade A, and why
fetch-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 4d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch PR Feedback
Fetch review comments from all reviewers on the current PR, format them, and evaluate using the receive-feedback skill. Excludes the PR author and current user by default. Line-specific comments belonging to resolved review threads are also excluded by default.
Usage
Invoke the fetch-pr-feedback skill, optionally passing these flags:
fetch-pr-feedback [--pr <number>] [--include-author] [--include-resolved]
Flags:
--pr <number>- PR number to target (default: current branch's PR)--include-author- Include PR author's own comments (default: excluded)--include-resolved- Include line-specific comments from resolved review threads (default: excluded)
Instructions
Gates (sequence; do not skip)
Advance only after each Pass when is satisfied.
- PR context — Pass when:
$PR_NUMBERis set to a positive integer andgh pr view/gh apifor that PR completed with exit code 0, or you stop in Get PR Context with only the failure given there (“No PR found for current branch…”). - Fetch — Pass when: the resolved-thread GraphQL call (skipped if
--include-resolved) and both paginatedgh api … | jq -s -f …runs (issue comments + review comments) exit 0 and parse as JSON (empty[]is valid). On non-zero exit or jq error, stop; surface command stderr—do not invent comments. - Formatted artifact — Pass when: output is either (a) markdown matching Format Feedback Document (header
# PR #$PR_NUMBER Review Feedback, per-reviewer## Reviewer: …with Summary / Line-Specific sections), or (b) exactly:No review comments found on this PR (excluding PR author, current user, and resolved threads). - Load receive-feedback — Pass when: the receive-feedback skill is loaded; only then run that skill’s verify → evaluate → execute loop on that formatted document.
1. Parse Arguments
Extract flags from $ARGUMENTS:
--pr <number>or detect from current branch--include-authorflag (boolean, default false)--include-resolvedflag (boolean, default false)
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.
- 4d ago First seen · 231 lines · 17 tokens per session scan A b67b730a292f
fetch-pr-feedback is a skill published in the GitHub repository existential-birds/beagle (79 stars, last pushed 25d ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,684 once invoked, about $0.0001 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-30.
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…