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 commands/robconery/kolea/git-prgit clone --depth 1 https://github.com/robconery/koleaWhat 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.00028 | $0.00556 |
| Opus 5 | $0.00014 | $0.00278 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
git-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.
This is a copy
100% identical to git-pr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
pr
Open a GitHub pull request for the current branch using the github
skill's PR template.
Behavior
- Preflight.
gh auth statusto confirm CLI is logged in.- Refuse if the current branch is
main— make a branch first (git switch -c <type>/<slug>). - Refuse if the working tree is dirty — commit or stash first
(suggest
/git-commit).
- Gather context in parallel:
git statusgit log <base>..HEAD --oneline(default base = the repo's default branch;mainunless--basearg says otherwise)git diff <base>...HEADto understand the full set of changes
- Push the branch if not already tracking a remote:
git push -u origin HEAD. - Draft per the
githubskill PR template:- Title — Conventional Commit style, ≤70 chars.
- Summary — 2–4 bullets covering all the commits, not just the latest. The headline change first.
- Why — one paragraph; link the story id / issue.
- How to verify — concrete checklist (commands, URLs, manual steps). Reviewer should be able to run these in order.
- Risk / rollback — one or two lines; be honest if it's low risk.
Closes #Nfooter if it resolves an issue.
- Show the draft to the user before creating. Confirm
--draftif work is still in progress. - Create with a HEREDOC body:
Usegh pr create --title "<title>" --body "$(cat <<'EOF' ... EOF )"--base <branch>only when not targeting the default.
Rules
- Title must reflect all the commits on the branch, not just HEAD.
- Don't push to
main; don't force-push to a branch with an open PR without saying so. - Don't include local-only paths, secrets, or
.envreferences in the body.
Hand off
Return the PR URL gh prints.
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 First seen · 57 lines · 28 tokens per session scan A 620a1dbc17ec
git-pr is a command published in the GitHub repository robconery/kolea (1 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 556 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to git-pr, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
sonicjs-pr-fixer
You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.
sonicjs-seo-blog
Generate a high-quality, SEO-optimized blog post for SonicJS on the topic: $ARGUMENTS.
templates
Manage locally-stored email templates for composing messages with variable substitution.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
hyperliquid-risk
Mission-critical real-time risk monitoring system with automated alerts, circuit breakers, and emergency shutdown for live Hyperliquid trading by ae.ltd.
migrate
Apply pending D1 migrations to local (default) or remote.