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/mfmezger/ai_agent_dotfiles/github-prnpx skills add mfmezger/ai_agent_dotfiles --skill github-prgit clone --depth 1 https://github.com/mfmezger/ai_agent_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.00065 | $0.01068 |
| Opus 5 | $0.00032 | $0.00534 |
| Sonnet 5 | $0.00013 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
github-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 2d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow
This skill guides the process of moving local changes to a GitHub Pull Request.
Prerequisites
gitmust be installed and configured.gh(GitHub CLI) must be installed and authenticated.
Commit Message Format
Use Conventional Commits with this required format:
<type>(<scope>): <summary>
typeREQUIRED. Common values:feat,fix,docs,refactor,chore,test,perf,ci,build,style.scopeREQUIRED. Short noun for the changed area (for example:config,api,ui,docs).summaryREQUIRED. Imperative, <= 72 chars, no trailing period.
Rules:
- Never add AI attribution anywhere in the GitHub workflow. Do not write
Generated by ...,Co-authored-by: Claude,Co-authored-by: Opus,Co-authored-by: Sonnet, or any other AI/model/agent attribution. - This ban applies to commit subjects, commit bodies, commit footers, PR titles, PR bodies, and PR comments. Do not add it even if a default template, tool, model habit, or previous workflow suggests it.
- Do not add sign-offs or breaking-change footers unless the user requests them.
Workflow Steps
Follow this order exactly: confirm branch state, stage, commit, push, then handle the PR.
-
Branch Check / Creation
- Check the current branch before doing anything else.
- If already on a suitable non-default working branch, stay on it.
- If on a default branch such as
mainormaster, create a feature branch first. - Identify the scope of changes (e.g.,
feat,fix,docs,chore). - Propose a branch name following the pattern
<type>/<kebab-case-description>. - Execute when a new branch is needed:
git checkout -b <branch-name>
-
Review & Stage Changes
- Review changes with
git statusandgit diff. - By default, stage only the files that belong to the current requested change.
- If the user provided file paths/globs, stage only those files.
- If there are ambiguous extra changed files, ask before staging/committing and leave them unstaged unless the user explicitly includes them.
- Stage the intended files with
git add .... - Optionally inspect recent subjects for local scope patterns:
git log -n 10 --pretty=format:%s.
- Review changes with
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.
- 2d ago First seen · 89 lines · 65 tokens per session scan A b70acba0f225
github-pr is a skill published in the GitHub repository mfmezger/ai_agent_dotfiles (5 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,068 once invoked, about $0.0003 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
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…
at-daily-log
Summarize each day's Git activity into a concise daily work log, for a single date or a range. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required.
at-commit
Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.
git-workflow
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…
github-sync-pr-flow
Use when preparing iPolloWork local changes for GitHub: stash or preserve local edits, sync the current personal branch with remote main, re-apply local work, diagnose conflicts, commit in English, push to the current remote branch, and open a PR to main without creating extra branches.
git-commit
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit…