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 rysh-ai/rysh-cli-code --skill pr-writergit clone --depth 1 https://github.com/rysh-ai/rysh-cli-codeWrote 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/rysh-ai/rysh-cli-code/pr-writer)<a href="https://agentmods.dev/skills/rysh-ai/rysh-cli-code/pr-writer"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/pr-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/rysh-ai/rysh-cli-code/pr-writer"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/pr-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.00014 | $0.00183 |
| Opus 5.5 | $0.00006 | $0.00073 |
| Sonnet 5.5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
pr-writer 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 1mo 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.
What it actually says
You write PR descriptions from what the branch actually changed.
Read git log for the range and git diff against the base branch before
writing a word. Describe the change that is there, not the change the commit
messages claim.
Structure
- What changed — one paragraph, plain sentences.
- Why — the problem it solves. If you cannot find the motivation in the code or commits, say "motivation not stated in the branch" rather than inventing one.
- Risk — what could break, and what is untested.
Rules
Do not pad. Do not restate the diff file by file — the diff is already in the PR. Do not claim a change is "tested" unless you found the test.
What ships with it
4 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.
- 1mo ago First seen · 24 lines · 14 tokens per session scan A 2ff51127aeab
pr-writer is a skill published in the GitHub repository rysh-ai/rysh-cli-code (5 stars, last pushed 11d ago), licensed Apache-2.0. It adds 14 tokens to every session and 183 once invoked, about $0.0001 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-31.
Other skills, from other repositories
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
pdf-processing
Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.
teamserver-git
Commit, branch and push a Mendix project in git the way Studio Pro and Mendix Team Server expect — branches created on the server (not with git checkout -b), the mxmetadata commit note written with mxcli git note, and the notes ref pushed with the branch. Use before any git commit, branch, merge, rebase or push in a…
knowledge-shell-process-and-worktree
Shell and Git worktree support for running commands, managing long-lived processes, and giving sessions isolated working directories. A Git worktree is a separate checkout linked to the same repository.