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/dotfiles/github-pull-requestnpx skills add fmind/dotfiles --skill github-pull-requestgit clone --depth 1 https://github.com/fmind/dotfilesWhat 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.00038 | $0.00610 |
| Opus 5 | $0.00019 | $0.00305 |
| Sonnet 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 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 — 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.
- yesterday 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 2d ago), licensed MIT. It adds 38 tokens to every session and 610 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-08-31.
Other skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
obsidian-bases
Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.
telegram
Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…
chezmoi-expert
Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…