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 fmind/dotfiles --skill github-pull-requestgit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/fmind/dotfiles/github-pull-request)<a href="https://agentmods.dev/skills/fmind/dotfiles/github-pull-request"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/github-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/fmind/dotfiles/github-pull-request"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/github-pull-request.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00610 |
| Opus 5.5 | $0.00015 | $0.00244 |
| Sonnet 5.5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
github-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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Pull Request
Create or update a GitHub pull request for the current branch against main.
Context Gathering
Gather context before drafting:
git fetch origin main— refreshorigin/mainso the ranges below are accurate.git config --get remote.origin.url— origin URL.git branch --show-current— current branch.git status --short— working tree state.gh pr view --json number,state,url— detect an existing PR for this branch (exits non-zero / empty when none, keying the create-vs-edit choice).git log --reverse --oneline origin/main..HEAD— commits sincemain.git diff --stat --find-renames origin/main...HEAD— diff stats.git diff --name-only --find-renames origin/main...HEAD— changed files.
Workflow
-
If the current branch is
main, stop and say a PR must come from a feature branch. -
Inspect changed files as needed so the PR matches the actual work, not just the commit subjects.
-
Write a clear PR title in imperative mood, under 72 characters.
-
Write a Markdown body with these sections:
## What ## Why ## How ## Test plan -
Push the current branch to
originwith upstream if needed (git push -u origin <branch>). -
If a PR already exists for this branch, update it:
gh pr edit --base main --title "<title>" --body-file <tmpfile> -
Otherwise create it:
gh pr create --base main --title "<title>" --body-file <tmpfile> -
Use a temporary file for the PR body instead of inline shell quoting.
-
After success, print the PR URL, the final title, and the final body.
-
If
origin/mainor GitHub auth is unavailable, explain the blocker briefly and stop.
Gotchas
- Keep the final response compact.
- Never force-push to
main.
Documentation
- feature-branch — branch creation upstream of the PR.
- conventional-commit — commit cadence on the branch.
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 First seen · 72 lines · 38 tokens per session scan A f64bfc81dc6e
github-pull-request is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 610 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-31.
Other skills, from other repositories
resolve-conflicts
Resolve Git merge or rebase conflicts by both sides' intent; verify the result.
github-repository
Set GitHub repo description, topics, merge policy, and security settings.
github-pull-request
Open, update, and verify GitHub pull requests.
git-worktree
Create Git branches, worktrees, or isolated snapshots of uncommitted work.
gh
Use gh for GitHub auth, repo selection, Actions logs, and bounded API calls.
repository-maintenance
Repository upkeep: fix tools, checks, dead code, stale config, and ignore files.