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/spideynolove/claude-dotfiles/commit-messagegit clone --depth 1 https://github.com/spideynolove/claude-dotfilesWhat 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.00016 | $0.01971 |
| Opus 5 | $0.00008 | $0.00986 |
| Sonnet 5 | $0.00003 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
commit-message 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message
Generates commit messages from staged changes (git diff --staged). This command only creates messages and copies them to your clipboard—it doesn't run any git commands.
Usage
/commit-message [options]
Options
--format <format>: Choose message format (conventional, gitmoji, angular)--lang <language>: Set language explicitly (en)--breaking: Include breaking change detection
Basic Examples
# Generate message from staged changes (language auto-detected)
# The top suggestion is automatically copied to your clipboard
/commit-message
# Specify language explicitly
/commit-message --lang ja
/commit-message --lang en
# Include breaking change detection
/commit-message --breaking
Prerequisites
Important: This command only works with staged changes. Run git add first to stage your changes.
# If nothing is staged, you'll see:
$ /commit-message
No staged changes found. Please run git add first.
Automatic Clipboard Feature
The top suggestion gets copied to your clipboard as a complete command: git commit -m "message". Just paste and run it in your terminal.
Implementation Notes:
- Run
pbcopyin a separate process from the message output - Use
printfinstead ofechoto avoid unwanted newlines
Automatic Project Convention Detection
Important: If project-specific conventions exist, they take priority.
1. CommitLint Configuration Check
Automatically detects settings from the following files:
commitlint.config.jscommitlint.config.mjscommitlint.config.cjscommitlint.config.ts.commitlintrc.js.commitlintrc.json.commitlintrc.yml.commitlintrc.yamlpackage.jsonwithcommitlintsection
# Search for configuration files
find . -name "commitlint.config.*" -o -name ".commitlintrc.*" | head -1
2. Custom Type Detection
Example of project-specific types:
// commitlint.config.mjs
export default {
extends: ["@commitlint/config-conventional"],
rules: {
"type-enum": [
2,
"always",
[
"feat",
"fix",
"docs",
"style",
"refactor",
"test",
"chore",
"wip", // work in progress
"hotfix", // urgent fix
"release", // release
"deps", // dependency update
"config", // configuration change
],
],
},
};
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 · 360 lines · 16 tokens per session scan A e9753d5dade7
commit-message is a command published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,971 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
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit
Smart commit that stages only conversation-relevant changes.
commit-all
Group all changes semantically and commit each group separately.
commit
Create a local git commit for source skills without pushing.
commit
This command helps you create well-formatted commits with conventional commit messages and emoji.
save
Command "save" from anton-abyzov/specweave, covering save changes across repositories, usage, interactive (prompts for commit message), dry run (show what would happen, don't execute) and save specific repos only (umbrella mode).