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/fmind/dot/github-pull-requestnpx skills add fmind/dot --skill github-pull-requestgit clone --depth 1 https://github.com/fmind/dotWrote 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/dot/github-pull-request)<a href="https://agentmods.dev/skills/fmind/dot/github-pull-request"><img src="https://agentmods.dev/badge/skills/fmind/dot/github-pull-request.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.00039 | $0.00685 |
| Opus 5 | $0.00019 | $0.00342 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pull Request
Create or update the pull request for the current branch against main with a What, Why, How, and Test plan body; feature-branch owns branch creation and conventional-commit the commits on it.
Workflow
-
Stop on
main: a PR must come from a feature branch. -
Gather context so the PR reflects the actual work, not only the commit subjects:
git fetch origin main # refresh origin/main for the ranges below git branch --show-current # current branch git status --short # working tree state gh pr view --json number,state,url # existing PR for this branch (non-zero exit when none) git log --reverse --oneline origin/main..HEAD # commits since main git diff --stat --find-renames origin/main...HEAD # diff stats git diff --name-only --find-renames origin/main...HEAD # changed files -
Write the title in imperative mood, under 72 characters.
-
Write the body into a temporary file (never inline shell quoting) with these sections:
## What ## Why ## How ## Test plan -
Push the branch with an upstream when it has none:
git push -u origin "$(git branch --show-current)". -
Create or update depending on step 2:
gh pr edit --base main --title "<title>" --body-file <tmpfile> # a PR exists gh pr create --base main --title "<title>" --body-file <tmpfile> # no PR yet -
Report the PR URL, the final title, and the final body; if
origin/mainor GitHub auth is unavailable, explain the blocker and stop.
Official Skills
Upstream: cli/cli. List the current release, then install what the task needs at project scope after reviewing the snapshot (see agent-skills):
gh skill preview cli/cli gh
gh skill install cli/cli gh
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 · 67 lines · 39 tokens per session scan A 3b69db462143
github-pull-request is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 685 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.