Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. 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/egregore-labs/egregore/main/.claude/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/pr)<a href="https://agentmods.dev/skills/egregore-labs/egregore/pr"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/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/egregore-labs/egregore/pr"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 22 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00052 | $0.00833 |
| Opus 5.5 | $0.00021 | $0.00333 |
| Sonnet 5.5 | $0.00010 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
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 24d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a pull request for current branch targeting the repo's base branch.
When to invoke
User says: "/pr", "create a PR", "open a pull request", "push this up for review", or the current branch is ready to be reviewed against the base branch.
Not this: reviewing an existing PR → /review-pr.
Execution boundary
The Git and GitHub mechanics are deterministic and run inline. The main loop keeps only the judgment work: summarize the diff, draft the review text, and show the exact title/body before the external PR creation.
What to do
- Determine which repo — if the user mentions a managed repo (listed in
egregore.json→repos[]), create the PR there. Otherwise use the hub. - Resolve the configured integration branch first:
It prints the branch name; for a managed repo runbash bin/base-branch.shbash bin/base-branch.sh <repo-name>. A non-zero exit means the configuration could not be resolved: stop before any Git change. Use the printed name wherever{base}appears below. - Summarize branch changes vs base branch
- Draft title and body per
.claude/context/pr-format.md:- Title:
type(scope): imperative summary(≤ 72 chars) — the same grammar as commit subjects (.claude/context/commit-format.md). A single-commit PR reuses its commit subject verbatim when it describes the whole PR. - Body:
## What(1–4 bullets) ·## Why(1–3 sentences) ·## Verification(how it was checked — required when the diff touches non-markdown files; be honest if unverified) ·## Risk/## Linkswhen real · attribution footer of the harness that authored the body (final non-blank line, e.g.🤖 Generated with [Claude Code](https://claude.com/claude-code)) - Show the draft to the user; apply their edits before creating
- Title:
- Create PR via GitHub CLI:
gh pr create --base "{base}" --title "$TITLE" --body "$BODY"— never--fill, never an empty body (thepr-formatCI check fails bare PRs) - Track PR in graph (fire-and-forget):
bash bin/graph-op.sh record-pr <number> "<title>" 2>/dev/null &<number>comes from thegh pr createoutput URL; the command resolves the session, repository, and author itself. - Return PR URL
- Do NOT auto-merge — explicit
/prmeans "please review this"
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.
- 24d ago Changed · -23 lines b4d7f6ffa00e
- 1mo ago First seen · 103 lines · 52 tokens per session scan A b000166ce08c
pr is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 833 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
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.