Borrowing it
Nothing to install: this file belongs to solana-foundation/solana-developer-platform. 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/solana-foundation/solana-developer-platform/main/.agents/skills/sdp-make-pr/SKILL.mdgit clone --depth 1 https://github.com/solana-foundation/solana-developer-platformWrote 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/solana-foundation/solana-developer-platform/sdp-make-pr)<a href="https://agentmods.dev/skills/solana-foundation/solana-developer-platform/sdp-make-pr"><img src="https://agentmods.dev/badge/skills/solana-foundation/solana-developer-platform/sdp-make-pr.svg" alt="Measured on agentmods" 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.00047 | $0.02111 |
| Opus 5 | $0.00023 | $0.01056 |
| Sonnet 5 | $0.00009 | $0.00422 |
| Haiku 4.5 | $0.00005 | $0.00211 |
Grade A, and why
sdp-make-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 3d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDP make PR
Prepare a reviewer-ready pull request for the current branch. First read ../sdp-concise/SKILL.md and apply its output contract to both the PR body and user updates.
This is an explicit PR-creation workflow. It may open a PR after the user approves the preview; it does not authorize committing, rebasing, pushing, force-pushing, or modifying code.
1. Pin the change set
- Read
AGENTS.md,CONTRIBUTING.md, the current branch, working-tree status, and any existing PR for the branch. - Default the base to
mainunless the user names another base. Inspect commits and the completebase...HEADdiff, including changed files and immediate callers needed to explain behavior. - If uncommitted changes exist, identify whether they belong to the PR and warn that they are absent from
base...HEAD. - If the branch is not pushed, ask before pushing. If a PR already exists, return its URL and ask before replacing its title or body.
Done when the exact committed change set and target base are known.
2. Build the title and body
Use this title format:
<type>(<module>): <high-level overview>
The module scope is required. Choose the type from the PR-title CI allowlist: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, or test. Use the SDP module changed by the PR as the scope, such as payments, issuance, wallets, api, web, or docs.
Example: feat(payments): add retryable settlement polling
Do not require or search for an issue ticket. Mention one only when the user explicitly asks for it.
Never emit one long flat bullet list: split the bullets under bolded section labels, adding bolded sub-labels when a section holds more than ~5 bullets (group by concern or domain). Dots always sit under a bolded label; a flat list is acceptable only for tiny PRs.
Write the body with a concise summary first and the technical behavior second. Explain only the changed seam: name the user-visible or operational result, the mechanism that produces it, the important failure semantics, and the evidence that verifies it. Omit unchanged architecture and background that does not help review the diff.
What ships with it
1 file 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.
- 3d ago Changed · +36 lines · +12 tokens per session 518eb7e0ff21
- 8d ago First seen · 103 lines · 35 tokens per session scan A 268e9d9b4b54
sdp-make-pr is a skill published in the GitHub repository solana-foundation/solana-developer-platform (52 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,111 once invoked, about $0.0002 per session on Opus 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.