Borrowing it
Nothing to install: this file belongs to chirino/memory-service. 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/chirino/memory-service/main/.skills/prepare-pull-request/SKILL.mdgit clone --depth 1 https://github.com/chirino/memory-serviceWrote 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/chirino/memory-service/prepare-pull-request)<a href="https://agentmods.dev/skills/chirino/memory-service/prepare-pull-request"><img src="https://agentmods.dev/badge/skills/chirino/memory-service/prepare-pull-request/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/chirino/memory-service/prepare-pull-request"><img src="https://agentmods.dev/badge/skills/chirino/memory-service/prepare-pull-request.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.00062 | $0.00295 |
| Opus 5.5 | $0.00025 | $0.00118 |
| Sonnet 5.5 | $0.00012 | $0.00059 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
prepare-pull-request 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
Prepare Pull Request
Run this workflow before invoking any commit or pull-request publishing workflow.
-
Inspect
git status --shortand preserve unrelated user changes. -
From the repository root, run:
task generateThis is the canonical generation and formatting command for the repository. Do not substitute narrower formatters for this required preflight.
-
If
task generatefails, diagnose the failure and stop PR submission until it succeeds. Do not submit a PR with partially generated output. -
Review
git status --shortand the complete diff after generation. Keep intended generated and formatting changes in the PR; do not silently discard unexpected changes. -
Run
git diff --checkand the verification required for the affected modules. Use thebuild-testskill to select those commands. -
Ensure every intended change produced by
task generateis committed before creating or updating the PR. If generation ran after the previous final commit, create the required follow-up commit before submission.
Report the task generate result and the verification performed when handing off the PR.
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.
- 1mo ago Changed · -1 tokens per session 2cac0a820ec7
- 2mo ago First seen · 24 lines · 63 tokens per session scan A 2784030143a8
prepare-pull-request is a skill published in the GitHub repository chirino/memory-service (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 62 tokens to every session and 295 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
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
otto-drive-pr
PR mergeability, CI, and live preview.
voicestudio-maintainer
Triage GitHub issues, review contributor pull requests, diagnose CI, and prepare explicitly requested releases for VoiceStudio's Electron desktop app and Python backend. Use for repository maintenance work, not ordinary VoiceStudio audio generation.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…