Borrowing it
Nothing to install: this file belongs to Terry-Mao/AICodingFlow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Terry-Mao/AICodingFlow/main/.agents/skills/git-push/SKILL.mdgit clone --depth 1 https://github.com/Terry-Mao/AICodingFlowWrote 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/terry-mao/aicodingflow/git-push)<a href="https://agentmods.dev/skills/terry-mao/aicodingflow/git-push"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/git-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/terry-mao/aicodingflow/git-push"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/git-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 19 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00017 | $0.00194 |
| Opus 5.5 | $0.00007 | $0.00078 |
| Sonnet 5.5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
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 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.
What it actually says
git-push
Use this after commits exist and the user asks to push or publish the current branch.
Check worktree status, current branch, upstream, and commits not yet on the
upstream. Refuse main, master, develop, and release branches unless the
user explicitly asks. Dirty changes are not pushed; report them and continue
only when pushing existing commits is clearly intended.
Use ordinary push for an existing upstream, otherwise set the branch upstream:
git push
git push -u origin <branch>
If rejected, fetch and inspect divergence. Ask before rebasing, merging, or
using --force-with-lease; never use plain --force unless explicitly
requested. Report branch, remote/upstream, pushed commit, result, and any dirty
changes left behind.
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 · 27 lines · 17 tokens per session scan A ff6afe4d01b9
git-push is a skill published in the GitHub repository Terry-Mao/AICodingFlow (169 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 194 once invoked, about $0.0001 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…