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.
git clone --depth 1 https://github.com/georgekhananaev/claude-skills-vaultWrote 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/commands/georgekhananaev/claude-skills-vault/git-push)<a href="https://agentmods.dev/commands/georgekhananaev/claude-skills-vault/git-push"><img src="https://agentmods.dev/badge/commands/georgekhananaev/claude-skills-vault/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/commands/georgekhananaev/claude-skills-vault/git-push"><img src="https://agentmods.dev/badge/commands/georgekhananaev/claude-skills-vault/git-push.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.00000 | $0.00969 |
| Opus 5 | $0.00000 | $0.00485 |
| Sonnet 5 | $0.00000 | $0.00194 |
| Haiku 4.5 | $0.00000 | $0.00097 |
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 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push Command
IMPORTANT: This command ONLY runs when explicitly invoked via /git-push. Do NOT auto-push after commits or modifications. Wait for user to explicitly run /push.
Goal: Safe git push with pre-push checks, commit integration, and changelog versioning.
1. Pre-Push Checks
Step 1: Check Uncommitted Changes
git status --porcelain
If output not empty (uncommitted changes exist):
- Ask user: "You have uncommitted changes. Run /git-commit first?"
- If YES: Execute commit command via
.claude/commands/git-commit.md, then continue - If NO: Abort push with message "Push cancelled - uncommitted changes exist"
Step 2: Check Remote Differences
git fetch origin
git log origin/$(git branch --show-current)..HEAD --oneline
If no commits ahead of origin:
- Inform user: "Nothing to push - branch is up to date with origin"
- Exit
2. Version Bump & Changelog
Step 1: Check for Unreleased Changes
- Read
CHANGELOG.mdand check if## [Unreleased]section has content - If empty: Skip version bump, proceed directly to push
- If has content: Continue to version selection
Step 2: Ask User for Version Bump
Use AskUserQuestion tool to prompt user:
Question: "Which version bump for this release?"
Options:
- Patch (+0.0.1) - Bug fixes, minor updates (Recommended)
- Minor (+0.1.0) - New features, backwards compatible
- Major (+1.0.0) - Breaking changes
- Skip - Don't create release, push as-is
Based on selection:
- Patch: Increment last number (1.0.0 → 1.0.1)
- Minor: Increment middle, reset last (1.0.5 → 1.1.0)
- Major: Increment first, reset others (1.2.3 → 2.0.0)
- Skip: Proceed to push without versioning
Step 3: Update CHANGELOG.md (if version selected)
- Replace
## [Unreleased]content with versioned release - Add today's date in format
YYYY-MM-DD - Create new empty
## [Unreleased]section above
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 · 123 lines · 0 tokens per session scan A fe88d1a09065
git-push is a command published in the GitHub repository georgekhananaev/claude-skills-vault (28 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 969 tokens. 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 commands, from other repositories
quick-commit
Quick commit with automatic formatting, linting, and conventional commit message.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
commit
Analyze Git changes and generate a conventional commit message following the Commitizen format.
commit
Generate a concise commit message for staged changes and commit.
fixup
Apply staged changes to a selected commit in history (rewrites history).
commit-push-pr
A command that creates a Git commit, sends it to a remote repository, and opens a pull request. A pull request is a request for others to review and merge code changes.