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 git-add-commit-pushgit 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/git-add-commit-push)<a href="https://agentmods.dev/skills/fmind/dotfiles/git-add-commit-push"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/git-add-commit-push/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/git-add-commit-push"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/git-add-commit-push.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.00047 | $0.00863 |
| Opus 5.5 | $0.00019 | $0.00345 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 1mo ago), licensed MIT. It adds 47 tokens to every session and 863 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
git-delivery
Stage, commit, push, and release scoped changes with Conventional Commits; fix hook failures.
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.
commit
Describe and finalize work with jj-vcs — drafting a description for the current change, splitting mixed work into focused commits, and advancing to a clean working copy. Use when asked to commit, when finishing a unit of work, or when starting new work on top of undescribed changes.
git-worktree
Create Git branches, worktrees, or isolated snapshots of uncommitted work.