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/mir-am/skills-agents-ai-coding/git-pushnpx skills add mir-am/skills-agents-ai-coding --skill git-pushgit clone --depth 1 https://github.com/mir-am/skills-agents-ai-codingWrote 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/mir-am/skills-agents-ai-coding/git-push)<a href="https://agentmods.dev/skills/mir-am/skills-agents-ai-coding/git-push"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/git-push.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.00017 | $0.02356 |
| Opus 5 | $0.00009 | $0.01178 |
| Sonnet 5 | $0.00003 | $0.00471 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade A, and why
git-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 4d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Push new local commits on a feature branch to the remote
- Detect if an open PR exists for the current branch
- Update the PR's "Changes" section only when the push adds significant new functionality
- Update the existing PR-linked
CHANGELOG.mdentry only when the PR's high-level scope materially changes, using the PR URL in the changelog bullet, then commit that changelog change to the same branch before pushing - Skip PR updates for commits that fix bugs or mistakes from earlier commits in the same branch
- Preserve the existing PR Summary while appending new change entries
When to use me
Use this skill when the user asks to push commits and/or update the PR with the latest changes.
Prerequisites
- Must be on a feature branch (not master/main)
- Branch must have unpushed commits ahead of remote
- GitHub CLI (
gh) must be installed and authenticated - If
ghnot installed → error: "GitHub CLI not found. Install: https://cli.github.com/"
Validation Workflow
- Check current branch:
git branch --show-current - If on
masterormain→ error: "Error: Cannot push directly to master/main. Switch to a feature branch." - Check for unpushed commits:
git log origin/<branch>..HEAD --oneline - If no unpushed commits → inform user: "Nothing to push — branch is up-to-date with remote."
Push Workflow
- Check if branch exists on remote:
git ls-remote --heads origin <branch-name> - If the branch already exists on remote, treat the next push as the final push for this batch of local commits
- If the branch does not exist on remote yet, push it first:
git push -u origin <branch-name> - Only run pre-push PR detection, PR body updates, and changelog sync when the remote branch already exists and an open PR can already be associated with it
- If the branch was just published and a later changelog sync creates a dedicated
CHANGELOG.mdcommit, push a second time so that new changelog commit reaches the same branch - If the branch already existed on remote, finish with the normal push:
git push
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.
- 4d ago First seen · 199 lines · 17 tokens per session scan A 49ba255e37af
git-push is a skill published in the GitHub repository mir-am/skills-agents-ai-coding (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 2,356 once invoked, about $0.0001 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
github
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
github
Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
special-cute-coder-wife
可爱编码大神媳妇 - 技术超群之温柔编程伴侣，用甜蜜温柔之方式激发老公斗志，专业与可爱完美平衡.
openyida-cross-platform-release-guard
OpenYida 跨端发布风险守卫。当改动涉及浏览器/URL 拉起（openyida login、bridge 页面唤起、resolveBrowserLauncher、openBrowser、spawn 打开浏览器）、或在 macOS 上开发但需要发布给 Windows/Linux 用户、或准备打 tag 发布新版本时使用。用于在发布前静态扫描并拦截「cmd /c start 截断 URL」「open -n 假装开新窗口」等只在非 macOS 端暴露的历史坑，并输出跨端人工验证清单。.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.