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/hackermanishackerman/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/hackermanishackerman/claude-skills-vault/git-push)<a href="https://agentmods.dev/commands/hackermanishackerman/claude-skills-vault/git-push"><img src="https://agentmods.dev/badge/commands/hackermanishackerman/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/hackermanishackerman/claude-skills-vault/git-push"><img src="https://agentmods.dev/badge/commands/hackermanishackerman/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.00758 |
| Opus 5.5 | $0.00000 | $0.00303 |
| Sonnet 5.5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
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.
How it starts
The opening of the file, as written. The whole thing — 105 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 /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 /commit first?"
- If YES: Execute commit command via
.claude/commands/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: Determine New Version
- Read current version from
CHANGELOG.md(find## [Unreleased]then next## [x.x.x]) - If latest version is
[1.0.0], new version =1.0.1(patch bump +0.0.1) - Format:
MAJOR.MINOR.PATCH
Step 2: Update CHANGELOG.md
- Replace
## [Unreleased]section header with versioned release - Add today's date in format
YYYY-MM-DD - Create new empty
## [Unreleased]section above
Before:
## [Unreleased]
### Added
- Feature X
## [1.0.0] - 2026-01-04
After:
## [Unreleased]
### Added
### Changed
### Fixed
## [1.0.1] - 2026-01-04
### Added
- Feature X
## [1.0.0] - 2026-01-04
Step 3: Commit Changelog
git add CHANGELOG.md
git commit -m "chore(release): bump version to X.X.X"
3. Execute Push
git push origin $(git branch --show-current)
On success: "Successfully pushed to origin"
On failure: Display error, do not retry automatically
4. Execution Flow Summary
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 · 105 lines · 0 tokens per session scan A c340b284ac55
git-push is a command published in the GitHub repository hackermanishackerman/claude-skills-vault (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 758 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-31.
Other commands, from other repositories
upgrade-project
Update existing project configurations to current best practices with selective component upgrades.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
justify
Audit changes for additive bias, Iron Law compliance, and minimal intervention. Justifies every change against a "simplest safe change" standard.
commit-claude-config
Un-ignore and commit the kit config (.claude/, CLAUDE.md, .mcp.json, .gitmodules).
quick-commit
Format, lint and commit with a conventional message on a kit-named branch.
project-init
Initialize a new project with git setup, CI/CD workflows, pre-commit hooks, Makefiles, and language-specific tooling.