kernl: Command for Claude Code

.claude/commands/title-commit.md

title-commit is a command for Claude Code from fastslack/kernl. It costs 19 tokens per session (1,166 once invoked), scanned A, original, Apache-2.0.

A command that groups files belonging to the current change and suggests a commit title. A commit is a saved snapshot in Git, but this command does not create one.

In plain words
What is it for?
It is for reviewing the working tree, staging related files, and matching the proposed title to the repository’s recent commit style.
Why use it?
It removes the need to inspect every changed file and invent a suitable title before committing manually.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is fastslack/kernl's own configuration. It tells Claude Code how to work on kernl 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 kernl configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fastslack/kernl. 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/fastslack/kernl/stable/.claude/commands/title-commit.md
Clone the repo
git clone --depth 1 https://github.com/fastslack/kernl

Made for: Claude Code.

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 title-commit

README.md
[![agentmods](https://agentmods.dev/badge/commands/fastslack/kernl/title-commit/github.svg)](https://agentmods.dev/commands/fastslack/kernl/title-commit)
Your own site
<a href="https://agentmods.dev/commands/fastslack/kernl/title-commit"><img src="https://agentmods.dev/badge/commands/fastslack/kernl/title-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 title-commit

Your own site · 80×15
<a href="https://agentmods.dev/commands/fastslack/kernl/title-commit"><img src="https://agentmods.dev/badge/commands/fastslack/kernl/title-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,166 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.00019 $0.01166
Opus 5.5 $0.00008 $0.00466
Sonnet 5.5 $0.00004 $0.00233
Haiku 4.5 $0.00002 $0.00117

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

Security

Grade A, and why

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

.claude/commands/title-commit.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

title-commit: $ARGUMENTS

Stage the files that belong to the current ongoing change and propose a commit title for it. Never run git commit — the user always commits manually.

Steps

1. Map the working tree

Run these in parallel:

  • git status --porcelain=v1 — list every modified, added, deleted, untracked file with its status code.
  • git diff --stat — magnitude of staged + unstaged changes.
  • git log --oneline -20 — recent commit message style (subject prefixes, casing, length).

2. Group changed paths by theme

A "theme" is a coherent unit of change. Detect it from path patterns. Common groupings in this repo:

  • Module: anything under services/kernel/src/modules/<name>/**. The module name is the theme.
  • Extension: anything under assets/extensions/<slug>/**. The slug is the theme.
  • Cross-module feature: when many modules + extensions share a topic (e.g. triage + github-channel + gitlab-channel + gitea-channel + services/kernel/assets/extensions/{triage,github,gitlab,gitea,*-channel,triage-orchestrator} all relate to "git/repo triage").
  • Dashboard: anything under services/dashboard/src/**.
  • Tests: anything under tests/** — usually grouped with the feature it tests.
  • Config / chore: top-level .env*, package.json, tsconfig*, docker-compose*.yml, services/kernel/scripts/**.

Skip files that are clearly noise:

  • Binary build artifacts: assets/extensions/*/backend/entry.js, dist/** — only stage these if the user explicitly asked, otherwise list them as "ignored from staging".
  • Lock files (package-lock.json, bun.lock) — include only if the related feature touched dependencies.
  • Backup files: *.bak-*, *.bak.

3. Pick the dominant theme

  • If $ARGUMENTS is provided, use that as the theme name and stage only files matching it.
  • Otherwise, count files per theme and pick the largest cohesive cluster.
  • If two or more themes have similar weight, stop and ask the user which one to stage — listing each theme with its file count and 3-5 sample paths.

Read the full file on GitHub · 110 lines

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 · 110 lines · 19 tokens per session scan A 4ad27bf17004

Subscribe to this mod's changes

title-commit is a command published in the GitHub repository fastslack/kernl (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 1,166 once invoked, about $0.0001 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

title-commit compared with commands from other repositories

title-commit next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
title-commitfastslack/kernlCommand3yesterdayApache-2.0A19Claude Code
quick-pushjmagar/claude-homelabCommand871mo agoMITA15Claude Code
gsd:undomrboups/xbrainCommand21mo agoMITA23Claude Code
gsd:quickmrboups/xbrainCommand21mo agoMITA24Claude Code
gsd:audit-fixmrboups/xbrainCommand21mo agoMITA25Claude Code
gsd:pause-workmrboups/xbrainCommand21mo agoMITA16Claude Code
gsd:pr-branchmrboups/xbrainCommand21mo agoMITA24Claude Code