Borrowing it
Nothing to install: this file belongs to zetaalphavector/RAGElo. 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/zetaalphavector/RAGElo/master/.agents/skills/create-pr-description/SKILL.mdgit clone --depth 1 https://github.com/zetaalphavector/RAGEloWrote 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/zetaalphavector/ragelo/create-pr-description)<a href="https://agentmods.dev/skills/zetaalphavector/ragelo/create-pr-description"><img src="https://agentmods.dev/badge/skills/zetaalphavector/ragelo/create-pr-description/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/zetaalphavector/ragelo/create-pr-description"><img src="https://agentmods.dev/badge/skills/zetaalphavector/ragelo/create-pr-description.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.00044 | $0.01643 |
| Opus 5.5 | $0.00018 | $0.00657 |
| Sonnet 5.5 | $0.00009 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
create-pr-description 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 2mo 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Description Generator Skill
Overview
This skill generates high-quality pull request descriptions for the RAGElo project by analyzing all changes, gathering context, and producing a human-readable summary. RAGElo is a Python library and CLI for evaluating RAG agents using Elo-based tournament ranking, published on PyPI.
Output Format
The agent must produce:
- PR Title - A concise, descriptive title (do NOT use conventional commits format like
feat(scope):orfix:) - PR Description - Human-readable summary of changes
- Proposed Reviewers - 1-2 people based on git history (excluding the PR author)
Step 1: Gather All Changes
Get the list of commits
git log origin/master..HEAD --oneline
Get the full diff
git diff origin/master..HEAD
Get list of changed files
git diff --name-only origin/master..HEAD
IMPORTANT: Do not just read commit messages. You MUST read the actual code changes to understand what was done. Commit messages may be incomplete or misleading.
Step 2: Gather Context
Read CLAUDE.md
Read CLAUDE.md at the repo root for project architecture, commands, and conventions.
Check for related issues (MANDATORY)
This step is required, not optional. Keyword searches often miss relevant issues. Use multiple approaches:
1. Browse recent open issues first (most reliable)
gh issue list --limit 50 --json number,title | jq -r '.[] | "\(.number): \(.title)"'
Scan issue titles manually - the tracking issue for your work may use different terminology than you'd search for.
2. Then search by keywords
gh issue list --search "<keyword1>" --json number,title | jq -r '.[] | "\(.number): \(.title)"'
gh issue list --search "<keyword2>" --json number,title | jq -r '.[] | "\(.number): \(.title)"'
Note: These searches default to open issues. If you need historical context on closed issues, add
--state closedexplicitly.
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.
- 2mo ago First seen · 234 lines · 44 tokens per session scan A 6983520e8d61
create-pr-description is a skill published in the GitHub repository zetaalphavector/RAGElo (133 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,643 once invoked, about $0.0002 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…