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 commands/fastslack/kernl/title-commitgit clone --depth 1 https://github.com/fastslack/kernlWhat 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.00019 | $0.01166 |
| Opus 5 | $0.00010 | $0.00583 |
| Sonnet 5 | $0.00004 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00117 |
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 yesterday.
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 — 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
$ARGUMENTSis 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.
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.
- yesterday First seen · 110 lines · 19 tokens per session scan A 4ad27bf17004
title-commit is a command published in the GitHub repository fastslack/kernl (1 stars, last pushed 9d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,166 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-08-31.
Other commands, from other repositories
validate-dependencies
Validate all task dependencies for issues.
flow-nexus-neural
Train and deploy neural networks in distributed sandboxes.
flow-nexus-auth
Flow Nexus authentication and user management.
validate-prd
Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.
editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension.
add-tool
Scaffold a new FreeAgent MCP tool (handler + registration + test) following the repo pattern.