Borrowing it
Nothing to install: this file belongs to nicepkg/vsync. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nicepkg/vsync/main/.claude/commands/commit.mdgit clone --depth 1 https://github.com/nicepkg/vsyncWrote 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/nicepkg/vsync/commit)<a href="https://agentmods.dev/commands/nicepkg/vsync/commit"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/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/nicepkg/vsync/commit"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/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.00006 | $0.00590 |
| Opus 5.5 | $0.00002 | $0.00236 |
| Sonnet 5.5 | $0.00001 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Git Commit
Create a git commit following Angular/Conventional Commits format. This repo uses semantic-release, so commit messages directly drive versioning.
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Staged diff: !
git diff --cached --stat - Unstaged diff: !
git diff --stat - Recent commits: !
git log --oneline -5
Instructions
Based on the changes above, create a single git commit.
Commit Format (Angular/Conventional)
type(scope): subject
Rules:
- Header must be <= 100 characters
- Type and scope must be lowercase
- Subject must be lowercase
- No period at the end of subject
- Use imperative mood: "add feature" not "added feature"
- Scope is optional, but if used must be one of:
website,docs,deps- Use
docsfor README/markdown only changes - Use
websiteforwebsite/changes
- Use
Commit Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Code style (formatting, semicolons, etc.) |
refactor |
Code change that neither fixes a bug nor adds a feature |
perf |
Performance improvement |
test |
Adding or updating tests |
build |
Build system or dependencies |
ci |
CI configuration |
chore |
Other changes (maintenance) |
revert |
Revert a previous commit |
Scope (optional)
Common scopes in this project:
website- website folder changesdocs- documentation only changesdeps- Dependenciescli- cli folder vsync package changes
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 · 82 lines · 6 tokens per session scan A dc51a6e6b0ff
commit is a command published in the GitHub repository nicepkg/vsync (61 stars, last pushed 9mo ago), licensed MIT. It adds 6 tokens to every session and 590 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
commit-message
Generate a conventional commit message from staged changes.
cg-oss-git-hygiene
Set up an open source repository for healthy long-term maintenance — branch protection, commit signing, tag immutability, issue and PR templates, CODEOWNERS, CONTRIBUTING.md, SECURITY.md, Dependabot, stale bot, and triage workflow. Use when the user is publishing an open source project, mentions branch protection…
commit
When you receive this command, do the following.
pre-commit-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
deploy
Deploy application with pre/post-deploy checks.