Berd is an open-source desktop application for working with AI agents through a graphical interface. It is intended for people who want to use different AI models and an integrated Goose backend from a desktop app. The catalogue entries add agent skills, agents, and instructions for working within Berd.
Borrowing it
Nothing to install: this file belongs to block/berd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/block/berd/main/.agents/skills/create-pr/SKILL.mdgit clone --depth 1 https://github.com/block/berdWrote 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/block/berd/create-pr)<a href="https://agentmods.dev/skills/block/berd/create-pr"><img src="https://agentmods.dev/badge/skills/block/berd/create-pr/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/block/berd/create-pr"><img src="https://agentmods.dev/badge/skills/block/berd/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.02289 |
| Opus 5.5 | $0.00030 | $0.00916 |
| Sonnet 5.5 | $0.00015 | $0.00458 |
| Haiku 4.5 | $0.00007 | $0.00229 |
Grade A, and why
create-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 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Create a GitHub PR from the current branch: handle uncommitted changes, generate a summary, submit, then watch the PR until it is in a ready state.
Step 1: Resolve Base Branch
Before doing anything else, identify the PR base branch. Prefer the branch's upstream base or the repository's default branch from git remote show origin. Fall back to origin/main only if the repo does not expose a default branch.
Remind the user to rebase onto the base branch if they have not already. Ask if they would like to proceed or rebase first.
Step 2: Check for Uncommitted Changes
Run git status to check for staged, unstaged, or untracked changes.
- If there are uncommitted changes, show the user what's outstanding and ask if they'd like to commit them before creating the PR.
- If the user says yes, stage the relevant files, draft a concise commit message based on the changes, and commit.
- If there are no uncommitted changes, move on.
Step 3: Gather Branch Context
Run these commands in parallel to understand the branch:
git log <base>..HEAD --onelineto see all commits on this branch.git diff <base>..HEAD --statto get the list of changed files.git diff <base>..HEADto understand what changed in each file.git rev-parse --abbrev-ref HEADto get the current branch name.git statusto check if the branch has been pushed to remote.
Step 4: Generate PR Title and Summary
Title: Generate a concise PR title (under 72 characters) that captures the intent of the change. Use conventional style: lowercase, imperative mood (e.g., "prevent chat list from reordering when renaming sessions").
Body: Generate a PR summary with these sections:
Section 1: Overview
Start with metadata tags, then a Problem/Solution block:
**Category:**— one of:new-feature,improvement,fix,infrastructure**User Impact:**— one sentence describing what changed from the user's perspective. Write this as a standalone sentence a non-technical stakeholder would understand (e.g., "Users can now create and schedule repeatable tasks directly from the desktop app."). This line is used for project changelogs.**Problem:**— describe the user-facing confusion, mismatch, or friction this PR addresses.**Solution:**— explain how the change resolves that UX problem and, if applicable, why the approach was chosen.
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 · 175 lines · 74 tokens per session scan A 1894698d118e
create-pr is a skill published in the GitHub repository block/berd (1,007 stars, last pushed 2d ago), licensed Apache-2.0. It adds 74 tokens to every session and 2,289 once invoked, about $0.0003 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-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.