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.
npx agentmods add skills/j-star-films-studios/vibecode-protocol-suite/git-commit-generationnpx skills add J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill git-commit-generationgit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/skills/j-star-films-studios/vibecode-protocol-suite/git-commit-generation)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/git-commit-generation"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/git-commit-generation.svg" alt="Measured on agentmods" 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.00024 | $0.00586 |
| Opus 5 | $0.00012 | $0.00293 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
git-commit-generation 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 2d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Generation
Generate clear, conventional git commit messages based on staged changes or recent repository diffs.
1. Workflow
-
Inspect Staged Diffs:
git status git diff --stagedIf no changes are staged, inspect unstaged changes with
git diffand suggest staging relevant files first. -
Analyze Scope & Purpose:
- Determine the primary type of change (e.g.
feat,fix,refactor,docs,test,chore). - Identify the affected scope or module (e.g.
cli,harness,skills,auth). - Isolate independent changes: if staged files span multiple distinct concerns, suggest splitting into separate commits.
- Determine the primary type of change (e.g.
-
Format Conventional Commit Message: Structure the message using the standard Conventional Commits format:
<type>(<scope>): <imperative summary in present tense> - Bulleted details explaining what changed and why - Key implementation decisions or removed legacy patterns
2. Commit Types
| Type | When to Use | Example |
|---|---|---|
feat |
New feature, capability, or user-facing addition | feat(skills): add code-intelligence umbrella suite |
fix |
Bug fix, error resolution, or regression patch | fix(cli): resolve timeout flakiness on windows |
refactor |
Code refactoring without changing behavior | refactor(store): unify skill materialization logic |
docs |
Documentation, guides, or specification updates | docs(architecture): sync lean unified taxonomy |
test |
Adding, updating, or fixing tests | test(lifecycle): verify heartbeat animation frames |
chore |
Maintenance, dependencies, or build config | chore(deps): bump pi-subagents to 0.31.0 |
3. Best Practices
- Imperative Mood: Write the header as a command (e.g.
feat(cli): add category treeinstead ofadded category tree). - Explain the Why: The body explains non-obvious reasoning and motivation, not merely a recap of file diffs.
- Breaking Changes: Highlight breaking changes clearly with
BREAKING CHANGE:in the footer or an exclamation mark after the type/scope (e.g.feat(api)!: update payload structure).
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.
- 2d ago First seen · 59 lines · 24 tokens per session scan A bbadfb4a16ce
git-commit-generation is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed today), licensed ISC. It adds 24 tokens to every session and 586 once invoked, about $0.0001 per session on Opus 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-09-03.
Other skills, from other repositories
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
setup-pre-commit
在当前仓库中设置 Husky pre-commit 钩子，集成 lint-staged（Prettier）、类型检查和测试。当用户想要添加 pre-commit 钩子、设置 Husky、配置 lint-staged、或添加提交时的格式化/类型检查/测试时使用。.
commit
Create well-formatted Git commits with conventional commit messages. Use this skill when the user wants to create a commit.
lean-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes…
kumihimo-iteration
Run ONE iteration of the Kumihimo build loop — take the next item off the queue, ground it against PLAN.md, build it, verify it, document it, commit it. Use when Thomas invokes /kumihimo-iteration (often wrapped in /loop for unattended runs) or asks for another build pass on Kumihimo. Covers the queue, verification…
commit
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.