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 VectorPeak/vectorpeak-agent-skills --skill pr-writer-vpgit clone --depth 1 https://github.com/VectorPeak/vectorpeak-agent-skillsWrote 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/vectorpeak/vectorpeak-agent-skills/pr-writer-vp)<a href="https://agentmods.dev/skills/vectorpeak/vectorpeak-agent-skills/pr-writer-vp"><img src="https://agentmods.dev/badge/skills/vectorpeak/vectorpeak-agent-skills/pr-writer-vp/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/vectorpeak/vectorpeak-agent-skills/pr-writer-vp"><img src="https://agentmods.dev/badge/skills/vectorpeak/vectorpeak-agent-skills/pr-writer-vp.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.00109 | $0.10694 |
| Opus 5.5 | $0.00044 | $0.04278 |
| Sonnet 5.5 | $0.00022 | $0.02139 |
| Haiku 4.5 | $0.00011 | $0.01069 |
Grade A, and why
pr-writer-vp 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 today.
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.
This is a copy
88% identical to pr-workflow-vp — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 554 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Writer
Use this skill for external open-source PR work. The workflow has six phases:
- Step1 Fork & Clone
- Step2 Find PR Chances
- Step3 Validate PR Value
- Step4 Implement & Create Formal PR
- Step5 Address Reviewer Feedback
- Step6 Refine PR Comment Section
Non-Negotiables
- Always start multi-agent work when this skill runs. Launch at least two agents before phase-specific work; use more for Step2, Step3, Step4, Step5, and Step6 when the repository is large, the task is ambiguous, reviewer feedback touches behavior-sensitive code, or a PR comment section needs stronger evidence.
- Treat submission as dry-run by default outside Step4 and Step5. Do not commit, push, create, mark ready, or update a PR unless the user explicitly asks for that action. When the user invokes Step4 by asking to create or submit a PR, treat that as permission to commit, push, and create a formal ready-for-review PR by default, unless the user explicitly asks for a draft PR.
- Do not modify
references/files as part of ordinary PR workflow. - Default clone path is
C:\XingyueZhu\Github\repos\<repo-name>on this Windows machine unless the user gives another path. - Prefer small, reviewable bug fixes. The default target is a production-code fix of 0-20 changed lines.
- Do not include unrelated refactors, generated churn, broad formatting, or
CHANGELOG.mdunless the project explicitly requires it. - Keep evidence honest. Distinguish runtime reproduction, UI reproduction, package reproduction, focused unit reproduction, inferred risk, and unavailable validation.
- Never add
Co-authored-bytrailers. Do not add bot co-authors, and do not add human reviewers as co-authors either. Commit authorship stays with the actual committer only. (User instruction, 2026-10-29: "Co-authored-by 目前不要去加这一段".) - Read
references/pr-examples.mdbefore drafting or revising PR prose. Treat it as the few-shot style guide for concise, evidence-driven bug-fix PRs. - PR delivery follow-ups (Step4 and Step5). After a PR is created or updated, do two things before reporting. Both are environment-dependent: ask once, then reuse the answer.
- Open the PR in whatever browser surface the current IDE actually provides. The IDE may be Qoder, WorkBuddy, Codex, or something else — do not hardcode a product or a tool name. Use the in-app browser/preview panel when the runtime exposes one; if not, report that the surface is unavailable and hand the raw URL to the user. Ask the user on the first run of a new IDE which surface they want.
- Produce a Chinese-translation Markdown copy of the PR body. Confirm the output location with the user on first use instead of assuming a fixed path; keep it outside the git work tree so it never pollutes the diff, and preserve the PR template headings, checkboxes, and status. The English body and the GitHub URL stay authoritative.
- Do not loop on summaries. When a phase completes and the only remaining work is waiting on an external event (maintainer review, CI, merge), report the final state once and hand control back to the user instead of re-printing the same summary on every "continue". Mark wait-on-review phases as
pending(orin_progresswith a "waiting for reviewer" note), nevercompleted; a phase is only complete when its deliverable exists. This is a default, not a hard rule: if the user asks to keep going, keep going.
What ships with it
3 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.
- today Changed · +11 lines a90a9f768dbd
- 2mo ago First seen · 543 lines · 109 tokens per session scan A a65b7e22143a
pr-writer-vp is a skill published in the GitHub repository VectorPeak/vectorpeak-agent-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 109 tokens to every session and 10,694 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to pr-workflow-vp, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…
write-git-messages
Draft, revise, or review Git commit messages, PR titles, PR descriptions, and squash or rebase merge messages. Use when Codex needs to summarize a diff for reviewers, convert rough notes into a commit or PR message, check a message against Git and Conventional Commits style, or prepare repository contribution text…
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…
ring:generating-release-guides
Generating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by…