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 krzysztofsurdy/code-virtuoso --skill pr-message-writergit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/pr-message-writer)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/pr-message-writer"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/pr-message-writer/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/krzysztofsurdy/code-virtuoso/pr-message-writer"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/pr-message-writer.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.00045 | $0.02593 |
| Opus 5.5 | $0.00018 | $0.01037 |
| Sonnet 5.5 | $0.00009 | $0.00519 |
| Haiku 4.5 | $0.00005 | $0.00259 |
Grade A, and why
pr-message-writer scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **If no UI exists** (API-only or GraphQL-only), provide the exact request to execute - full query/mutation with example variables, which tool to use (GraphQL playground, Postman, curl), and the exact URL/endpoint How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Message Writer
Write structured pull request descriptions by analyzing the code changes and following the template in this skill.
Workflow
Step 1: Gather context
-
Determine the main branch:
git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'Fall back to
mainormasterif this is not set. -
Find the merge base:
MAIN_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "main") MERGE_BASE=$(git merge-base HEAD origin/$MAIN_BRANCH) -
Collect all changes since the branch diverged:
git log --oneline $MERGE_BASE..HEAD git diff --stat $MERGE_BASE..HEAD git diff $MERGE_BASE..HEAD -
If a ticket ID or branch name is provided as an argument, include it in the PR title.
-
Gather ticket context. You need the ticket content to write accurate testing instructions and to understand the business requirement. If it is available in context (e.g., from a previous conversation or your project tracker), use it. If it is not available or has dropped out of context, ask the user to provide it before proceeding. Do not guess or invent requirements.
Step 2: Analyze changes
Read every changed file and understand:
- What was changed (new files, modified logic, deleted code)
- Why the change was made (bug fix, new feature, refactoring, performance)
- Impact on existing functionality (breaking changes, migrations, cache invalidation)
- Dependencies introduced or removed
Step 3: Follow the template
Use the PR message template for structure: template
Review real-world examples for tone and detail level: examples
Every PR, whatever its type, carries two short sections after "What have I changed":
- Merge danger: Reversibility (one-way or two-way door, with one line of why) and Blast radius (the scope of impact in a word or phrase). Judge both from the diff, not from the ticket.
- Evidence: a screenshot or recording is strongest, then execution or test output, then a before/after. Ask the user for the highest tier the change allows, and state which tier the PR uses.
What ships with it
2 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.
- yesterday Changed · +8 lines accb050813e1
- 3d ago Changed · -8 tokens per session dc044a29988d
- 1mo ago First seen · 188 lines · 53 tokens per session scan A 1ac94e40e9e5
pr-message-writer is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 2,593 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
skill-creator
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating…
openclaw-pr-maintainer
Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
code-review-report
Turn code changes into a single-file HTML code review report that pairs the diff with context a diff can't show — design decisions, rejected alternatives, tradeoffs, unfinished work — plus prioritized review points. Use when preparing for review after finishing a sizable change, refactor, or feature, or whenever the…
impl
A code-review workflow that checks whether an implementation matches the project's agreed plan and evaluation criteria. It uses `.claude/context.md` as the reference document.