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/git-add-commit-pushnpx skills add fmind/dotfiles --skill git-add-commit-pushgit 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.00047 | $0.00863 |
| Opus 5 | $0.00023 | $0.00432 |
| Sonnet 5 | $0.00009 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
git-add-commit-push 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Add, Commit, and Push
Wraps the commit-subject rules from conventional-commit, then stages, commits, and pushes — auto-healing lefthook pre-commit/pre-push failures along the way.
Workflow
-
Check Working Directory & Staging State:
- Run
git branch --show-currentand record it — committing and pushing directly tomain/masteris allowed and is the normal flow. Branch first via the feature-branch skill only when the user asked for a PR flow, or when the push is later rejected by branch protection. - Check if there are staged changes:
git diff --cached --name-only. - If nothing is staged, check if there are unstaged changes:
git status --short. - If there are unstaged changes, stage them using
git addto prepare for commit. - If the working tree is completely clean and nothing is staged, say so and stop.
- Run
-
Generate Commit Message:
- Craft the commit subject using the naming rules from the conventional-commit skill (
<type>(<scope>): <description>, imperative mood, under 72 chars). Do NOT run its commit/stop-on-failure steps — this skill performs the commit and auto-heals hook failures below.
- Craft the commit subject using the naming rules from the conventional-commit skill (
-
Commit Stage (Pre-Commit Hook Auto-Healing):
- Run
git commit -m "<subject>"to commit the staged changes. - If the commit fails (pre-commit hook failure):
- Read the hook output carefully to diagnose the issues.
- Formatting/Linting: Run the project's
mise run formatandmise run checktasks. - Type checking / Tests: Run type verification checks or compiler checks to resolve error states.
- Once the issues are resolved, stage the affected files (
git add) and retry the commit with the same message. - Repeat this troubleshooting loop until the commit succeeds, or report the blocker if manual intervention is required.
- Run
-
Push Stage (Pre-Push Hook Auto-Healing):
- Identify the current branch using
git branch --show-current. - Run
git push(remote tracking is set up automatically viapush.autoSetupRemote). - If the push fails due to a pre-push hook failure (the
testhook runningmise run test—pytest/gotestsum):- Read the test runner output to identify the failing tests.
- Debug and fix the bugs in the code or tests.
- Stage the fixes (
git add), amend the commit (git commit --amend --no-edit), and retry the push. - Repeat until the push succeeds, or report the remaining failures if manual intervention is required.
- Identify the current branch using
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 · 63 lines · 47 tokens per session scan A 8825279222e6
git-add-commit-push is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 863 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…