Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Benknightdark/neo-skillsnpx agentmods add skills/benknightdark/neo-skills/neo-prWrote 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/benknightdark/neo-skills/neo-pr)<a href="https://agentmods.dev/skills/benknightdark/neo-skills/neo-pr"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-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/benknightdark/neo-skills/neo-pr"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.01392 |
| Opus 5 | $0.00030 | $0.00696 |
| Sonnet 5 | $0.00012 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
neo-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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neo PR Generator & Refiner
neo-pr is an expert skill engineered to generate precise, concise, and non-AI-slop Pull Request (PR) titles and descriptions for Git repositories. It proactively guides the user to clarify repository and branch targets, extracts change histories, and outputs clear, highly structured PR content.
Gotchas
- Non-existent or Unaligned Branches: If the specified source or target branch does not exist locally or on remote, prompt the user to run
git fetchor provide the correct branch name. Do not invent non-existent base branches. - Overly Long Diffs and Token Overhead: If the branch diff spans dozens of files or thousands of lines, inspect
git diff --statand commit logs first to gain high-level context instead of loading full diffs at once. - De-slop Does Not Mean Removing Technical Substance: When stripping AI fluff, eliminate throat-clearing openers (e.g., "It is worth noting that...", "This PR aims to..."), but strictly preserve essential context, key logic shifts, breaking changes, and test instructions.
Workflow Checklist
- Step 1 — Perceive (Gather Branch & Repository Context): Identify the repository path, source branch (
source branch), and target branch (target branch). If unspecified, prompt the user or detect the current Git state. - Step 2 — Reason & Load References (Load Templates & Guidelines): Read pr-template.md for structural standards and de-slop conventions.
- Step 3 — Act: Extract Diff (Fetch Change Record): Execute the helper script
git-pr-extractor.pyto retrieve commit logs, file statistics, and diff snippets. - Step 4 — Act: Generate & De-slop (Produce Concise PR Content): Write a Conventional Commits title and bulleted PR description while eliminating all AI tells.
- Step 5 — Verify (Quality Check): Verify that the generated title and description adhere to de-slop standards (optionally run
analyze-slop.jsto score density).
What ships with it
4 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.
- 11d ago First seen · 115 lines · 60 tokens per session scan A b115d682a2f6
neo-pr is a skill published in the GitHub repository Benknightdark/neo-skills (7 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 1,392 once invoked, about $0.0003 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
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…
fetch-pr-comments
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the…
reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".
reply-to-pr-conversation
Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments). The reply addresses all tracked items in one natural-prose message. Use when the user asks to "reply to PR conversation", "post PR conversation replies", or "draft PR conversation messages".
review-pr
Review a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".
git-pr-review
A read-only reviewer for GitHub pull requests, which are proposed code changes submitted for review. It produces an evidence-based report about whether a pull request should be merged.