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 lucasnad27/claude-plugins --skill prepare-prgit clone --depth 1 https://github.com/lucasnad27/claude-pluginsWrote 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/lucasnad27/claude-plugins/prepare-pr)<a href="https://agentmods.dev/skills/lucasnad27/claude-plugins/prepare-pr"><img src="https://agentmods.dev/badge/skills/lucasnad27/claude-plugins/prepare-pr.svg" alt="Measured on agentmods" 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.00036 | $0.03780 |
| Opus 5 | $0.00018 | $0.01890 |
| Sonnet 5 | $0.00007 | $0.00756 |
| Haiku 4.5 | $0.00004 | $0.00378 |
Grade A, and why
prepare-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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare PR
You are tasked with getting a change ready for review: commit any outstanding work, open a pull request, and land a review guide that points human attention at what matters. You don't replace code review — you make it faster by saying where to look, anchored to the lines it's about.
Write and Edit are for the PR body, the review payload, and any source fix the user explicitly asks for during a walkthrough — never for unprompted changes.
This is the final step of the research → design → plan → implement → review workflow.
Mark the herdr phase
As your very first action, tag this agent's herdr tab so the session navigator shows the workflow phase (safe no-op outside herdr):
bash "$(git rev-parse --show-toplevel)/.claude/scripts/herdr-phase.sh" review
Initial Response
Determine the mode from $ARGUMENTS:
- No arguments → Create mode. Commit outstanding changes on the current branch, push, open a new PR, land the guide.
- A PR number (e.g.
123) → Update mode. Leave existing commits alone; write the guide onto that PR. Use this when a PR was created outside this skill loop. - A branch name → Create mode targeting that branch's diff against the default branch.
Flags, anywhere in $ARGUMENTS:
--no-stops— keep the whole guide in the PR description; post no inline comments.--walk/--no-walk— force or suppress the Step 7 walkthrough without asking.
If the mode is ambiguous, state your assumption and proceed; don't stall on a question you can answer from context.
The review guide is a numbered list of stops
One artifact, three places it appears:
- Inline review comments on the PR — the detail, anchored to the line it's about. This is its home.
- A numbered index in the PR description — one line per stop, so the guide is legible without opening the diff.
- A tuicr session, if the author walks it — GitHub review threads render natively in
tuicr pr <n>, so a posted review needs no seeding.
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 a544dfd0e155
- 7d ago First seen · 256 lines · 36 tokens per session scan A 165d0e2568b4
prepare-pr is a skill published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 3,780 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-08-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.