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 YangsonHung/awesome-agent-skills --skill git-pushing-fastgit clone --depth 1 https://github.com/YangsonHung/awesome-agent-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/yangsonhung/awesome-agent-skills/git-pushing-fast)<a href="https://agentmods.dev/skills/yangsonhung/awesome-agent-skills/git-pushing-fast"><img src="https://agentmods.dev/badge/skills/yangsonhung/awesome-agent-skills/git-pushing-fast/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/yangsonhung/awesome-agent-skills/git-pushing-fast"><img src="https://agentmods.dev/badge/skills/yangsonhung/awesome-agent-skills/git-pushing-fast.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.00053 | $0.01388 |
| Opus 5 | $0.00026 | $0.00694 |
| Sonnet 5 | $0.00011 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
git-pushing-fast 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 10d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Pushing Fast
Overview
Commit and push the current repository's local changes on the current branch with a fast, safe single-branch workflow.
The default output is one focused Conventional Commit plus a push to the tracked remote branch. Analyze the actual diff, stage the requested change set, generate the commit message from the change content, and write a segmented body for non-trivial changes so reviewers can quickly see what changed by topic.
This workflow handles ordinary single-branch handoff requests such as saving current work to the remote, without branch merging, history rewriting, or PR creation.
Conventional Commit Rules
Base format:
<type>[optional scope]: <description>
[body: optional only for trivial changes; required and segmented for non-trivial changes]
[footer(s): required for breaking changes; optional for relevant issue references]
For this skill, the body is optional only for trivial commits. For non-trivial changes, write a segmented body and include a Tests: or localized equivalent section when tests, validators, hooks, or manual verification ran.
Types:
| Type | Use for |
|---|---|
feat |
New user-facing or product capability |
fix |
Bug fix |
docs |
Documentation-only change |
style |
Formatting/style change with no logic impact |
refactor |
Code restructure with no feature or bug fix |
perf |
Performance improvement |
test |
Test-only or test coverage change |
build |
Build system, dependency, or packaging change |
ci |
CI or automation config change |
chore |
Maintenance or miscellaneous change |
revert |
Revert a previous commit |
Breaking changes:
- Use
!after the type or scope, such asfeat(api)!: remove legacy field. - Add a
BREAKING CHANGE:footer when the behavioral contract changes.
Message style:
- Use the repository's existing commit language.
- Write the subject in present tense and imperative mood, such as
fix login redirect. - Keep the subject under 72 characters when practical.
- Reference issues in the body or footer when relevant, such as
Closes #123orRefs #456.
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.
- 10d ago First seen · 139 lines · 53 tokens per session scan A 74d73fbba2d0
git-pushing-fast is a skill published in the GitHub repository YangsonHung/awesome-agent-skills (18 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,388 once invoked, about $0.0003 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-30.
Other skills, from other repositories
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
stage
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
commit-staged-push
Commit already-staged changes and push in one step. Use when the user asks to "commit and push staged changes", "commit and push what's staged", or "commit staged and push".