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.10275 |
| Opus 5 | $0.00055 | $0.05137 |
| Sonnet 5 | $0.00022 | $0.02055 |
| Haiku 4.5 | $0.00011 | $0.01027 |
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 8d 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.
This is a copy
88% identical to pr-writer-vp — 15 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 — 543 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
D:\ZXY\Github\<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.
- For every commit created while using this skill, explicitly include the relevant Codex/GitHub bot as a
Co-authored-bytrailer when a valid bot noreply identity can be verified. Prefer the active reviewer bot identity when responding to bot review feedback, for exampleCo-authored-by: chatgpt-codex-connector[bot] <199175422+chatgpt-codex-connector[bot]@users.noreply.github.com>. Do not guess bot IDs or emails; verify them with GitHub user metadata such asgh api users/<bot-login>before committing. - When a commit implements a substantive human reviewer's requested change, best-effort include that reviewer as an additional
Co-authored-bytrailer using a valid GitHub noreply or otherwise verified public email. Never guess private emails; skip the human trailer if the identity cannot be verified or if the repository's norms discourage human co-authorship. - 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.
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.
- 8d 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 1mo ago), licensed Apache-2.0. It adds 109 tokens to every session and 10,275 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to pr-writer-vp, differing in 15 lines, and is treated as a copy.
Other skills, from other repositories
hub-cc-pr-reviewer
Checks a submitted PR against the environment's baseline assets (CLAUDE.md, memory, naming, asset classification) and attaches a review comment with a merge recommendation. 5 steps — diff read, 8-area consistency check, self-catch, comment, merge recommendation.
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…
open-pr
Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.