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-commit)<a href="https://agentmods.dev/commands/hackermanishackerman/claude-skills-vault/git-commit"><img src="https://agentmods.dev/badge/commands/hackermanishackerman/claude-skills-vault/git-commit/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-commit"><img src="https://agentmods.dev/badge/commands/hackermanishackerman/claude-skills-vault/git-commit.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.00946 |
| Opus 5.5 | $0.00000 | $0.00378 |
| Sonnet 5.5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
git-commit 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Command
IMPORTANT: This command ONLY runs when explicitly invoked via /commit. Do NOT auto-commit after code modifications. Wait for user to explicitly run /commit.
Goal: Safe, attributed git commit for the configured git user.
1. Identity & Attribution
- Author: Use
git config user.name&git config user.email(linked GitHub account) - Credit: No co-authors/AI attribution unless requested
2. Safety Protocols
Forbidden Files:
- Secrets:
.env,.env.*,*.pem,*.key,id_rsa,secrets.*,credentials.* - Logs:
*.log,npm-debug.log,yarn-error.log - System:
.DS_Store,node_modules/,dist/,build/,__pycache__/,.venv/
Critical Flags:
- No
--no-verify(hooks must pass) - No
--no-gpg-sign(sign if GPG configured) - No
--amend(unless fixing immediate prev commit)
3. Version Control (Interactive)
Prompt: "Update project version?"
If YES:
- Detect:
package.json|pyproject.toml|setup.py|Cargo.toml|VERSION - Bump: Major (+1.0.0) | Minor (+0.1.0) | Patch (+0.0.1)
- Execute: Update file → Stage → Commit
4. Execution Flow
git status- check stategit diff- review (stop if secrets/debug found)- Version check (above)
- Stage:
git add <file>(use-pfor mixed changes, avoidgit add .w/ junk) - Construct message (Conventional Commits)
git commit -m "..."git status- verify
5. Commit Message Standard
Format: <type>(<scope>): <description>
| Type | Desc |
|---|---|
| feat | new feature |
| fix | bug fix |
| docs | docs only |
| style | formatting |
| refactor | no fix/feat |
| perf | performance |
| test | tests |
| build | build/deps |
| ci | CI config |
| chore | other |
| revert | revert commit |
Rules: Imperative mood, no period, max 72 chars, scope opt but recommended
6. Grouping
- Atomic: Split unrelated changes into separate commits
- Ask: "Changes in X & Y. Separate commits?"
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 · 131 lines · 0 tokens per session scan A dad69435e0cf
git-commit 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 946 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.