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 skills add TweekFawkes/prompts --skill openprgit clone --depth 1 https://github.com/TweekFawkes/promptsWrote 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/tweekfawkes/prompts/openpr)<a href="https://agentmods.dev/skills/tweekfawkes/prompts/openpr"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/openpr.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.1 | $0.00118 | $0.02193 |
| Opus 5 | $0.00059 | $0.01097 |
| Sonnet 5 | $0.00024 | $0.00439 |
| Haiku 4.5 | $0.00012 | $0.00219 |
Grade A, and why
openpr 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 8d 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.
/openpr — Push the current worktree and open a PR into main
You are wrapping up work in a git worktree and want it reviewed/merged through GitHub rather than fast-forwarded locally. The goal: every change in this worktree lands on a feature branch, that branch is pushed to origin, and a pull request targeting main is open (or refreshed) on github.com — leaving the actual merge to a human on the PR page.
This is the remote counterpart to /gohome. /gohome lands work on main locally and never pushes; /openpr pushes the branch and opens a PR and never merges. Pick this one when the change should go through review.
Authoritative facts (verify, don't assume)
- Remote:
origin→ your GitHub repo. Confirm withgit remote -v. - Base branch:
main. - CLI: use the
ghCLI for all GitHub operations (confirm it's authenticated withgh auth status). Never hand-craft API calls or ask the user to click around ifghcan do it. - Branch naming: feature branches follow your convention (e.g.
<username>/<slug>); agent branches may becodex/<slug>orclaude/<slug>. Use the branch that's already checked out — do not rename it. - Merge style: if the repo merges PRs as
Merge pull request #N from <branch>with the PR title as the merge subject, write the PR title as the real change summary. - Worktree gitignored artifacts: a worktree may carry seeded, gitignored local state (env files, dependency/build caches). These do NOT appear in
git status(they're ignored) and must never be force-added.
Required workflow
1. Reconnaissance (always run first, in parallel)
git remote -v
git worktree list
git branch --show-current
git status --short
git diff --stat HEAD
git log --oneline -5
git fetch origin
git log --oneline origin/main..HEAD # commits this branch adds
git log --oneline HEAD..origin/main # commits main has that we don't
gh pr list --head "$(git branch --show-current)" --state open --json number,url,title
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.
- 8d ago First seen · 139 lines · 118 tokens per session scan A e3bb53178999
openpr is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 118 tokens to every session and 2,193 once invoked, about $0.0006 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
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.