knowledgine: Skill for Claude Code

.agents/skills/git-commit/SKILL.md

git-commit is a skill for Claude Code, Codex from 3062-in-zamud/knowledgine. It costs 92 tokens per session (1,285 once invoked), scanned A, original, MIT.

A commit-writing and commit-planning tool that follows Conventional Commits, a shared format for describing changes in Git history. It can preview messages and detect breaking changes.

In plain words
What is it for?
Use it when creating, suggesting, splitting, or correcting Git commits, including when deciding whether a change is a feature, fix, documentation update, or other type.
Why use it?
It prevents inconsistent commit messages, unnecessary ticket references, and commits that combine unrelated changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is 3062-in-zamud/knowledgine's own configuration. It tells Claude Code and Codex how to work on knowledgine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything knowledgine configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 3062-in-zamud/knowledgine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/3062-in-zamud/knowledgine/develop/.agents/skills/git-commit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/3062-in-zamud/knowledgine

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for git-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/git-commit/github.svg)](https://agentmods.dev/skills/3062-in-zamud/knowledgine/git-commit)
Your own site
<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/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.

agentmods 80×15 button for git-commit

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,285 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.01285
Opus 5.5 $0.00037 $0.00514
Sonnet 5.5 $0.00018 $0.00257
Haiku 4.5 $0.00009 $0.00128

Measured 2mo ago against content hash dd0ae04d787d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.agents/skills/git-commit/SKILL.md · 181 lines

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
  • NEVER include scope in parentheses — use feat: not feat(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.

Read the full file on GitHub · 181 lines

Files

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.

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.

  1. 2mo ago First seen · 181 lines · 92 tokens per session scan A dd0ae04d787d

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 1,285 once invoked, about $0.0004 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-31.

Related

git-commit compared with skills from other repositories

git-commit next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
git-commit3062-in-zamud/knowledgineSkill33mo agoMITA92Claude Code, Codex
create-prprisma/ormSkill48kyesterdayApache-2.0A48Claude Code, Codex
git-commitThinkInAIXYZ/deepchatSkill6.4kyesterdayApache-2.0A15Claude Code, Codex
repo-syncdavidondrej/skillsSkill4.3k3d agoMITA25Claude Code, Codex
engineer-bot-opsmakecindy/cindySkill9.3kyesterdayApache-2.0A57Claude Code, Codex
mcore-split-prNVIDIA/skillsSkill3.9kyesterdayApache-2.0A25Claude Code
git-commit-writermergisi/awesome-openclaw-agentsSkill4.1k2d agoMITA53Claude Code, Codex