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/zhaoyis/my-skills/git-commit-pushnpx skills add ZhaoYis/My-Skills --skill git-commit-pushgit clone --depth 1 https://github.com/ZhaoYis/My-SkillsWrote 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/zhaoyis/my-skills/git-commit-push)<a href="https://agentmods.dev/skills/zhaoyis/my-skills/git-commit-push"><img src="https://agentmods.dev/badge/skills/zhaoyis/my-skills/git-commit-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.00030 | $0.01205 |
| Opus 5 | $0.00015 | $0.00602 |
| Sonnet 5 | $0.00006 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
git-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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 185 lines · 30 tokens per session scan A b9c06879f573
git-commit-push is a skill published in the GitHub repository ZhaoYis/My-Skills (2 stars, last pushed 4d ago), with no licence file. It adds 30 tokens to every session and 1,205 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
awesome-git-history-rebuild
Erases a repository's git history and rebuilds it as a curated commit series over the same tree: a split plan the user approves (proposed here, or supplied by awesome-commit-plan and validated first), the repo's own commit rules obeyed (commitlint, hooks, CONTRIBUTING), paced timestamps anchorable to the earliest…
awesome-git-author-rewrite
Rewrites the author and committer identity on a commit — or on every commit carrying a wrong identity — and force-pushes it, safely: account-ownership and write-access checks, a verified mirror backup, a counted hash blast radius, and an explicit confirmation gate before anything irreversible. Takes a commit URL plus…
awesome-commit-plan
Turns a codebase into a commit plan: a navigation map of its modules and their dependency direction, then a split where every commit builds and tests on its own, so the series is bisectable end to end. Each commit is verified by replaying the ladder in a scratch clone against the repository's own gates, never…
awesome-git-history-reset
Erases a repository's entire git history and replaces it with a single fresh commit, then force-pushes — safely: access checks, a verified mirror backup, a secret scan, and an explicit confirmation gate before anything irreversible. Use when asked to 'wipe git history', 'squash all commits into one', 'reset history to…
summarize-issue
After an issue is fixed and its MR is created, summarize the work in high-level markdown and post it as a comment on the GitLab issue.
git-workflow
Trunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.