Borrowing it
Nothing to install: this file belongs to frostney/pascal-mcp-sdk. 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/frostney/pascal-mcp-sdk/main/.agents/skills/create-pr/SKILL.mdgit clone --depth 1 https://github.com/frostney/pascal-mcp-sdkWrote 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/frostney/pascal-mcp-sdk/create-pr)<a href="https://agentmods.dev/skills/frostney/pascal-mcp-sdk/create-pr"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/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/frostney/pascal-mcp-sdk/create-pr"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/create-pr.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.00043 | $0.00678 |
| Opus 5.5 | $0.00017 | $0.00271 |
| Sonnet 5.5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
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.
What it actually says
Create PR
The request authorizes the repository's declared gates, relevant fixes and commits, plain pushes, PR metadata updates, one draft pull request, and its transition to ready for review. It does not authorize unrelated changes.
- Inspect the working tree, staged diff, recent commits, and remote default branch.
- Stop if there are no relevant changes or commits ahead of the remote base. Continue without an empty commit when the work is already committed.
- If currently on the base branch, create a focused branch named from the issue or change.
- Run the repository's declared pre-PR gate unless it already passed on the unchanged current diff. Never claim an unobserved result.
- Stage only relevant files, excluding secrets and unrelated local work.
- Commit uncommitted work with a concise Conventional Commit subject. Never amend and never skip hooks.
- Push normally, setting upstream when needed. Never force-push.
- Fill the matching PR template, preserving its structure. If none exists, use
Summary, Testing, and Linked issues. Keep the body proportional to the change.
Put each closing keyword on its own line:
Closes #N. - Open one draft PR against the remote default branch.
- Find the nearest applicable
DEFINITION_OF_READY.md. If it exists, compare every criterion with the actual PR diff, tests, documentation, linked work, metadata, and validation evidence to identify anything the PR is missing. If absent after a real search, use this workflow's built-in gates. - Fill every in-scope readiness gap. Add missing implementation, tests, documentation, or artifacts, or correct the PR body and links. For repository changes, validate, create a new commit, and push normally; metadata-only fixes require no commit. Never mark a criterion satisfied without observed evidence.
- Monitor every applicable CI check to a terminal result. While a check is not green, inspect its logs, fix the in-scope root cause without weakening the gate, run the relevant local checks, create a new commit, push normally, and monitor the new run.
- Keep the PR in draft while any readiness criterion or CI check is pending or failing. Continue monitoring pending checks; if they cannot reach a terminal result during the run, report their current state. Stop and report the exact blocker when satisfying it requires a material product decision, unrelated work, unavailable external service, or a change that cannot be validated safely.
- Once the PR is missing nothing required by the Definition of Ready and all applicable CI is observed green, mark it ready for review. Return its URL, final state, fixes made, and observed readiness and CI evidence.
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 · 57 lines · 43 tokens per session scan A 6ec52188dcd2
create-pr is a skill published in the GitHub repository frostney/pascal-mcp-sdk (2 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 678 once invoked, about $0.0002 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
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
git-workflow
Trunk-based git workflow with worktrees, switch/restore over checkout, Conventional Commits, force-with-lease. Use whenever the user asks me to commit, push, branch, or rebase.
project-briefing
Generate an executive briefing of the last 24 hours of commits for the current project or a specified directory. Use when the user asks for a project update, daily briefing, commit summary, "what changed today," or wants to stay up-to-date with recent work.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
issue
Create a GitHub issue using the Dedalus issue templates (bug, feature, question). Injects branch and commit context automatically, prompts for Linear link. Use when creating a GitHub issue using Dedalus templates, or the user says "file an issue", "create issue", "open a bug", or "report a feature request".
oss-workflow
Open-source project success workflow for viznoir. Codifies contributor onboarding, release management (Release Please + PyPI), issue triage, and showcase curation. Triggers: release, contributor, onboarding, PyPI publish, issue triage, showcase, CHANGELOG, good first issue.