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/3062-in-zamud/knowledgine/git-commitnpx skills add 3062-in-zamud/knowledgine --skill git-commitgit clone --depth 1 https://github.com/3062-in-zamud/knowledgineWrote 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/3062-in-zamud/knowledgine/git-commit)<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/git-commit"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/git-commit.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 | $0.00092 | $0.01285 |
| Opus 5 | $0.00046 | $0.00642 |
| Sonnet 5 | $0.00018 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
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 4d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Create clean, meaningful commits following Conventional Commits.
Core Rules
Format: <type>: <description>
feat: add hybrid search fallback to keyword mode
Gracefully degrade to keyword search when embedding
provider is unavailable, with user-facing warning.
BREAKING CHANGE: searchMode option "auto" removed, use "hybrid" instead
Strict prohibitions:
- NEVER include ticket numbers, issue IDs, or internal references in the subject line
- Bad:
feat: add search KNOW-305 - Bad:
fix: resolve #123 crash - OK in footer only:
Closes #123
- Bad:
- NEVER include scope in parentheses — use
feat:notfeat(cli): - No trailing period in description
- No capitalized first letter in description
Description rules:
- Imperative mood ("add" not "added", "fix" not "fixes")
- Lowercase start
- Max 72 characters
- One commit = one logical change
Type Reference
| Type | When to use | Semver impact |
|---|---|---|
feat |
New feature or capability | minor |
fix |
Bug fix | patch |
docs |
Documentation only | patch |
style |
Formatting, whitespace (no logic change) | patch |
refactor |
Code change that neither fixes nor adds | patch |
perf |
Performance improvement | patch |
test |
Add or update tests | patch |
chore |
Maintenance, deps, tooling | patch |
ci |
CI/CD configuration | patch |
build |
Build system changes | patch |
revert |
Revert a previous commit | patch |
Breaking changes (! suffix or BREAKING CHANGE: footer) → major
Breaking Change Detection
Before committing, scan staged changes for these patterns. If detected, use feat!: or fix!: prefix and add BREAKING CHANGE: footer.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 181 lines · 92 tokens per session scan A dd0ae04d787d
git-commit is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,285 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…