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 agentmods add skills/frostney/pascal-mcp-sdk/create-prnpx skills add frostney/pascal-mcp-sdk --skill create-prgit 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.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.00678 |
| Opus 5 | $0.00022 | $0.00339 |
| Sonnet 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 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.
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.
- 3d 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 7d ago), licensed MIT. It adds 43 tokens to every session and 678 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-31.
Other skills, from other repositories
prepare-release
Run all GocciaScript release-preparation tasks before /create-release — verify the build is green, sync docs and the website to source truth (numbers and claims), preview the changelog, run the conformance and generated-data checks, and open a prep PR — ending strictly before the version/changelog/tag work that…
profile-report-review
Review GocciaScript retained VM profile reports from test262 and benchmark main-CI runs. Use when Codex is asked to inspect uploaded test262 or benchmark performance/profile artifacts, compare week-over-week or main-run trends, investigate aggregate/detailed profile data, or turn profiling findings into compiler…
gocciascript-issue-validation
Validate GocciaScript engine issues against the project-specific test262 harness. Use alongside implement-issue for GocciaScript issues that mention test262, ECMA-262/ECMA-402 conformance, Intl, or parser compatibility flags.
implement-idea
Turns an unfiled idea into a confirmed mini-spec, implements and validates the selected approach, reviews it, and opens a draft pull request. Use when the user runs /implement-idea or asks to build something without an existing issue.
implement-issue
Validates and implements a GitHub issue against current repository evidence, runs the project's completion gate, reviews the change, and opens a draft pull request. Use when the user runs /implement-issue with an issue number.
review-pr
Resolves current pull-request review findings in place, validates and pushes fixes, and can autonomously converge and merge an opted-in pull request. Use when the user runs /review-pr or /review-pr automatic-merge.