Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/GocciaScript/main/.agents/skills/create-pr/SKILL.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/gocciascript/create-pr)<a href="https://agentmods.dev/skills/frostney/gocciascript/create-pr"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/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/gocciascript/create-pr"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/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.00059 | $0.02640 |
| Opus 5.5 | $0.00024 | $0.01056 |
| Sonnet 5.5 | $0.00012 | $0.00528 |
| Haiku 4.5 | $0.00006 | $0.00264 |
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 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.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Publish the current change as a verified, accurately described pull request
that is ready for review. The request authorizes the repository's declared
gates, relevant commits, PR metadata updates, one ordinary draft pull request or
the confirmed native stack layers owned by the change, required review and
behavior testing, in-scope fixes, and transitions to ready for review. This
includes the project's existing PR preview path when required to test the
change. Merge and integration delivery belong to /deliver, which a direct
request continues into under the
delivery settings; the request does not add
unrelated changes.
A failed check, review or CI run routes to repair, not a stop. Stop only when there is nothing to publish, a material unresolved choice or new authority is needed, or an external blocker remains after safe alternatives are exhausted. A material choice that publication depends on stops before any push or draft PR. Keep the PR draft while any required evidence or CI is missing, pending or failing.
Conditional references
- When the branch belongs to a native GitHub stack or builds on an unmerged PR (step 1), read ../git-workflow/references/github-stacks.md. The request then authorizes submission and metadata reconciliation for the confirmed stack layers owned by the current change, not unrelated branches.
- When the change has visible or demonstrable behavior, or local screenshots or videos belong in the PR, read references/walkthroughs.md. It owns media capture, upload and gap reporting. Never commit evidence media to the repository. Missing media capabilities alone do not block publication or readiness; required behavior evidence and project gates still apply.
Preview-only draft
When required behavior can only be tested on a PR preview, open or update the draft needed to obtain it under this publication request after the available checks pass. Publish a native stack's necessary drafts through the same permitted stack path. Test that exact revision and resume the loop before readiness. Recording a walkthrough does not replace behavior testing.
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.
- yesterday Changed · +23 lines 53e127064543
- 11d ago Changed · +1 lines c44ad4fd3032
- 22d ago Changed · +6 lines 5fef4a8c7c7c
- 24d ago Changed · +33 lines 100f9bdc1342
- 26d ago Changed · +6 lines · +18 tokens per session bbadb8f4a78e
- 29d ago Changed · +49 lines · -2 tokens per session 3a2f26bbf477
- 1mo ago First seen · 75 lines · 43 tokens per session scan A 14b0c456b037
create-pr is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 2,640 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-30.
Other skills, from other repositories
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
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.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.