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 eric861129/SKILLS_All-in-one --skill git-pushinggit clone --depth 1 https://github.com/eric861129/SKILLS_All-in-oneWrote 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/eric861129/skills_all-in-one/git-pushing)<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/git-pushing"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/git-pushing/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/eric861129/skills_all-in-one/git-pushing"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/git-pushing.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.00070 | $0.00246 |
| Opus 5 | $0.00035 | $0.00123 |
| Sonnet 5 | $0.00014 | $0.00049 |
| Haiku 4.5 | $0.00007 | $0.00025 |
Grade A, and why
git-pushing 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 9d 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.
This is a copy
100% identical to git-pushing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Git Push Workflow
Stage all changes, create a conventional commit, and push to the remote branch.
When to Use
Automatically activate when the user:
- Explicitly asks to push changes ("push this", "commit and push")
- Mentions saving work to remote ("save to github", "push to remote")
- Completes a feature and wants to share it
- Says phrases like "let's push this up" or "commit these changes"
Workflow
ALWAYS use the script - do NOT use manual git commands:
bash skills/git-pushing/scripts/smart_commit.sh
With custom message:
bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature"
Script handles: staging, conventional commit message, Claude footer, push with -u flag.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 32 lines · 70 tokens per session scan A d54394e9e9af
git-pushing is a skill published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo ago), licensed MIT. It adds 70 tokens to every session and 246 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to git-pushing, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
campaign-commit
Choose the correct commit command in a camp, also called a campaign. Use when you are about to commit and need to select camp commit, camp p commit, fest commit, or intentional root pointer sync via camp refs-sync.
roadmap-task-deliver
Deliver the first eligible unfinished roadmap task through implementation, review, green CI, PR merge, and a task-status update. Use for autonomous delivery from local roadmap and task files. Files can be outside the code repository or outside Git.
pr-review-fix-pipeline
Autonomous PR review that also applies fixes for non-controversial issues — combines review, fix, test, and commit into a single pipeline. Unlike a read-only review, this writes code. Only use on feature branches where you're comfortable with automatic edits. Trigger on: "review and fix PR", "auto-fix the PR", "clean…
phase-commit
Create one local commit for a completed, validated, and reviewed unit of work. Use only when the user explicitly requests a commit without pushing or other delivery actions.
shipit
Turn finished work into a clean commit and pull request. Always asks first whether the commit and PR should carry AI/bot authorship attribution or stay fully human-authored, then matches the repository's existing commit conventions, splits work into logical commits, and writes a PR body with context, risk, and…