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 racecraft-lab/racecraft-plugins-public --skill speckit-resolve-prgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/racecraft-lab/racecraft-plugins-public/speckit-resolve-pr)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-resolve-pr"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-resolve-pr/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/racecraft-lab/racecraft-plugins-public/speckit-resolve-pr"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-resolve-pr.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.00048 | $0.01553 |
| Opus 5 | $0.00024 | $0.00776 |
| Sonnet 5 | $0.00010 | $0.00311 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
speckit-resolve-pr 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit Resolve PR
Capability discovery & grounding
Before researching or recommending, enumerate the tools and skills your session actually exposes — do not assume a fixed set; the user may have installed anything — and select the best fit per speckit-pro/skills/speckit-autopilot/references/capability-discovery.md. Ground every external fact you assert in a real tool, skill, or file result per speckit-pro/skills/speckit-autopilot/references/grounding.md, and abstain when nothing grounds it.
Scope
Use this skill when the user wants review feedback addressed on an existing pull request. The goal is not a general code review. The goal is to read the unresolved review feedback, make the necessary code changes, verify the branch, reply to the review comments, and resolve the threads.
If the user wants a fresh review of a PR, use a review workflow instead. If
they want to learn how the post-PR loop works, redirect to $speckit-coach.
This skill is for remediation and closure.
Input
Accept either:
- a pull request number
- a pull request URL
- a review-comment URL anchored to a specific PR review
If only a PR number is supplied, derive the repository from git remote -v.
Never assume the remote is named origin; inspect the actual remotes first.
Preconditions
Before editing anything:
- ensure the current checkout is on the PR branch or switch to it safely, and verify the actual code behavior in that checkout; never review or remediate from the diff alone
- confirm
ghis available and authenticated if thread resolution is required - inspect the repo state with
git statusso you know whether unrelated user changes are already present
Do not overwrite unrelated dirty worktree changes. If the current checkout cannot safely host the remediation, create or switch to the correct branch without discarding existing work.
Discover Project Verification Commands
Read the project guidance files and package manifests to determine the real verification commands. For JavaScript or TypeScript projects, detect the package manager from the lockfile before running anything. Capture, when available:
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.
- 2d ago Changed · +11 lines 267a20fa1514
- 8d ago First seen · 175 lines · 48 tokens per session scan A 4ac4d6f387d2
speckit-resolve-pr is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,553 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-09-04.
Other skills, from other repositories
gsd-pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
git-workflow
Git best practices, branching strategies, commit conventions, and code review patterns.
task-to-pr
Completes one or more tasks. Creates one tested and reviewed pull request for each task. Use to implement, build, fix, or deliver tasks, tickets, pull requests, or a milestone.
speq-git-discipline
Read-only git guardrails and the Conventional Commits reference — no history writes, verify changes before completing. Triggered by planner-agent, implementer-agent, implementer-expert-agent, and recorder-agent. The headless orchestrators speq-plan-pr and speq-implement-pr are the sole exception: they write git…
implement-suggestion
Implements review-comment suggestions across one or more PRs. Multi-PR mode (default when $ARGUMENTS contains PR URLs; empty $ARGUMENTS auto-detects the active PR) per PR: resolves a worktree, fetches every actionable comment from both human teammates AND AI code-review bots (claude[bot], coderabbitai[bot], …)…
pr-review
One-shot read-only review of a GitHub PR — dispatches the pr-reviewer agent and reports its verdict and findings without touching your code. The short entry point for "review this PR" when you do not want an apply-and-converge loop. Also writes maintainer relevance rules via /pr-review remember . Invoke with…