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.
git clone --depth 1 https://github.com/magic3007/dotfilesWrote 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/commands/magic3007/dotfiles/smart-commit)<a href="https://agentmods.dev/commands/magic3007/dotfiles/smart-commit"><img src="https://agentmods.dev/badge/commands/magic3007/dotfiles/smart-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.
<a href="https://agentmods.dev/commands/magic3007/dotfiles/smart-commit"><img src="https://agentmods.dev/badge/commands/magic3007/dotfiles/smart-commit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00026 | $0.02424 |
| Opus 5.5 | $0.00010 | $0.00970 |
| Sonnet 5.5 | $0.00005 | $0.00485 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
smart-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 1mo 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Commit
Analyze all currently staged git changes, group them by logical concern, and create multiple well-structured commits following Conventional Commits v1.0.0.
Usage
/smart-commit [--dry-run]
Arguments:
--dry-run: Only show the proposed commit plan without executing
Conventional Commits Specification
Every commit message MUST follow this format:
<type>[optional scope][optional !]: <description>
[optional body]
[optional footer(s)]
Types
| Type | When to Use |
|---|---|
feat |
A new feature (correlates with MINOR in SemVer) |
fix |
A bug fix (correlates with PATCH in SemVer) |
docs |
Documentation only changes |
style |
Formatting, missing semi-colons, etc. (not CSS) |
refactor |
Code change that neither fixes a bug nor adds a feature |
perf |
Performance improvement |
test |
Adding or correcting tests |
build |
Changes to build system or external dependencies |
ci |
Changes to CI configuration files and scripts |
chore |
Other changes that don't modify src or test files |
revert |
Reverts a previous commit |
The 50/72 Rule & Formatting Rules
Subject line (first line):
- Separate subject from body with a blank line — the subject is used in
git log --oneline,git shortlog, etc. - Limit the entire subject line to ~50 characters (type + scope + description combined). Hard limit: 72 chars.
- Capitalize the description after
<type>(scope):— e.g.,feat(auth): Add JWT refresh, NOTfeat(auth): add JWT refresh - No period at the end of the subject line
- Use imperative mood — "Fix bug", "Add feature", NOT "Fixed bug" or "Adds feature". The subject should complete: "If applied, this commit will _____."
- All commit messages in English
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.
- 1mo ago First seen · 335 lines · 26 tokens per session scan A bab7d8ab8c2c
smart-commit is a command published in the GitHub repository magic3007/dotfiles (11 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 2,424 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.
Other commands, from other repositories
push-commit
Create a new commit from the current repo changes and push it.
commit
Create a new commit from the current repo changes.
commit
Follow the Commit messages rule in the repository AGENTS.md when present; otherwise use the Conventional Commits 1.0.0 summary below.
commit
Stage all changes and create a Conventional Commit, optionally pushing to remote.
issue-implement
Pick up GitHub issue $ARGUMENTS.
pr
Create a GitHub PR from the current repo changes.