Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add KnowledgeXLab/skill-git/plugin install skill-gitWrote 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/knowledgexlab/skill-git/commit)<a href="https://agentmods.dev/commands/knowledgexlab/skill-git/commit"><img src="https://agentmods.dev/badge/commands/knowledgexlab/skill-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/knowledgexlab/skill-git/commit"><img src="https://agentmods.dev/badge/commands/knowledgexlab/skill-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.00050 | $0.01911 |
| Opus 5.5 | $0.00020 | $0.00764 |
| Sonnet 5.5 | $0.00010 | $0.00382 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
skill-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 2mo 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /skill-git:commit. Follow these steps exactly.
Task Tracking
You MUST create a task for each item below and update each task's status as you progress (pending → in_progress → completed):
- Scan for changes — warn about unregistered skills, then parallel-scan all skills for diffs
- Display change summary — show what changed and ask the user which skills to commit
- Suggest versions and messages — analyze diffs, propose semver bumps and commit messages
- Execute commits — run git add, commit, tag, and update config.json for confirmed skills
Prelude
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/sg-prelude.sh" $ARGUMENTS
If STATUS is not ok:
- Re-examine RAW_ARGUMENTS — check if the user expressed an agent name or intent that can be semantically resolved (e.g. a typo, a paraphrase, or an implicit default).
- If you can determine intent, note the resolution (e.g. "Treating
-a cluadeasclaude") and proceed. - If STATUS is
not_initializedand INITIALIZED_AGENTS is non-empty, suggest the user run/skill-git:init -a <agent>, or mention which agents are already available. - If STATUS is
error, display REASON as a plain-language error and stop. - If intent cannot be resolved, display a clear error and stop.
Use AGENT, GLOBAL_BASE, and SKILLS_JSON from prelude output for all subsequent steps. The skills map referred to throughout this document is the parsed content of SKILLS_JSON.
Agent name in positional position: If $ARGUMENTS contains a known agent name (claude, gemini, codex, openclaw) as a standalone positional token not preceded by -a, silently treat it as -a <agent>: override AGENT, re-read GLOBAL_BASE and SKILLS_JSON from ~/.skill-git/config.json for that agent. Do not pass it to any skill-name parsing steps.
Step 1a — Filesystem Scan
Run:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/sg-warn-unregistered.sh" "<global_base>" '<skills_json>'
Display the output if any (do not stop, do not prompt).
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.
- 2mo ago First seen · 184 lines · 50 tokens per session scan A 1b67ee778375
skill-git:commit is a command published in the GitHub repository KnowledgeXLab/skill-git (42 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 1,911 once invoked, about $0.0002 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
replay
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
Create well-formatted commits with conventional commit messages and emojis.
genshijin-commit
A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.
evolve-lite-unpublish
Remove your published entity from a write-scope repository and restore a private copy.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.