Borrowing it
Nothing to install: this file belongs to baijum/ukulele-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/baijum/ukulele-companion/main/.cursor/skills/pr-groups/SKILL.mdgit clone --depth 1 https://github.com/baijum/ukulele-companionWrote 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/baijum/ukulele-companion/pr-groups)<a href="https://agentmods.dev/skills/baijum/ukulele-companion/pr-groups"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/pr-groups/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/baijum/ukulele-companion/pr-groups"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/pr-groups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 229 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00094 | $0.02947 |
| Opus 5 | $0.00047 | $0.01473 |
| Sonnet 5 | $0.00019 | $0.00589 |
| Haiku 4.5 | $0.00009 | $0.00295 |
Grade A, and why
pr-groups 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 10d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Groups
Arguments: $ARGUMENTS
Turn a set of open issues into groups, each of which one PR can close, plus the order to land them in.
This is the opposite of maximizing parallelism. Two issues in the same function belong in one PR even though that serializes them — splitting them means two reviews of the same code and a merge conflict between your own branches.
This is a two-platform repo (Android/Kotlin + iOS/Swift) over a shared KMP
module. That changes the grouping in one specific way, threaded through every
step below: a fix in shared/src/commonMain/ lands once and fixes both
platforms, while a bug that lives on only one platform — very common here,
where issues are usually filed as Android-vs-iOS parity divergences — touches
only that platform's files. Always know which of the three surfaces an issue
sits on (shared / android / ios) before grouping it.
1. Scope the set
Interpret the argument:
| Argument shape | Query |
|---|---|
| empty | gh issue list --state open --limit 500 --json number,title,labels,assignees |
label:<name> |
add --label "<name>" (repeat per comma-separated label; they AND). This repo's practical filters are the priority labels P0 / P1 / P2 and the area labels audio / ui / music-content / accessibility / testing / ci-cd. |
| a milestone title | add --milestone "<title>" — but milestones are rarely set here; expect an empty result and fall back to asking whether the user meant a label. |
| comma-separated numbers | fetch exactly those with gh issue view <n> --json number,title,labels,body,state,assignees; drop any whose state is not OPEN, and say which you dropped |
If a filter returns nothing, say so and stop. Never silently widen to the whole tracker. If the returned count equals the limit, raise the limit and rerun.
Drop from consideration, and say which you dropped and why: epics and tracking
issues, issues already assigned, issues with an open linked PR, and anything
labelled blocked / wontfix / duplicate / invalid.
What ships with it
1 file 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.
- 10d ago First seen · 238 lines · 94 tokens per session scan A af1878d58499
pr-groups is a skill published in the GitHub repository baijum/ukulele-companion (14 stars, last pushed 7d ago), licensed MIT. It adds 94 tokens to every session and 2,947 once invoked, about $0.0005 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
sceneview-ios
Build 3D and AR apps on Apple platforms (iOS, macOS, visionOS) with SceneViewSwift — the SwiftUI wrapper around RealityKit. Use whenever the user asks for "3D in SwiftUI", "AR with ARKit in SwiftUI", a model viewer for iOS, or any Apple-platform 3D/AR app where the dependency is the SceneViewSwift Swift Package from…
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
sceneview-web
Build 3D and WebXR (AR/VR) experiences in the browser with SceneView for Web — Filament.js (WebGL2/WASM) wrapped in a Kotlin/JS DSL and a plain-JavaScript API on window.sceneview. Use whenever the user asks for "3D in the browser", "a web model viewer", "WebXR AR/VR", or any browser 3D/AR app where the dependency is…
to-plan
Use when one ready GitHub issue or an in-chat task needs a repository-aware implementation plan for a later implementation workflow.
compose-ui-testing-patterns
Use when writing or reviewing Jetpack Compose UI tests, screenshot tests, previews, semantics assertions, fake image loading, keyboard input, focus assertions, interaction state (hover/pressed/focused), or tests for plain state-driven UI composables.
gradle-run
Use when planning to execute Gradle through gradle, ./gradlew, or a custom gradlew wrapper script, or diagnosing a Gradle build, compact workflow ledger, repeated failure fingerprint, check, test, lint, warning, or failure even when no new Gradle run is appropriate.