Borrowing it
Nothing to install: this file belongs to conectlens/lenserfight. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/conectlens/lenserfight/main/.agents/skills/smart-commit/SKILL.mdgit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/skills/conectlens/lenserfight/smart-commit)<a href="https://agentmods.dev/skills/conectlens/lenserfight/smart-commit"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/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/skills/conectlens/lenserfight/smart-commit"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/smart-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.01664 |
| Opus 5.5 | $0.00029 | $0.00666 |
| Sonnet 5.5 | $0.00015 | $0.00333 |
| Haiku 4.5 | $0.00007 | $0.00166 |
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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Commit
Inspect the working tree, classify every change first, group into logical commits, then handle each commit separately with explicit user approval.
Never commit without user confirmation. Never lump unrelated changes into one commit.
Workflow
Step 1 — Snapshot the working tree
Run all three commands and keep the output in context:
git status --short
git diff --stat HEAD
git diff --cached --stat
If both staged and unstaged areas are empty, tell the user there is nothing to commit and stop.
Step 2 — Read the full diff
# Staged changes
git diff --cached
# Unstaged changes
git diff
Skim hunks to understand what changed, not just which files. Treat both staged and unstaged as candidates — classification covers everything.
Step 3 — Classify ALL changes (REQUIRED FIRST STEP)
This step is mandatory before any staging or committing decision is made.
Map every changed file (staged or unstaged) to a conventional-commit type:
| Type | When to use |
|---|---|
feat |
New user-visible feature or capability |
fix |
Bug fix or incorrect behavior corrected |
refactor |
Code restructuring with no behavior change |
perf |
Performance improvement |
test |
Adding or updating tests only |
docs |
Documentation, comments, README only |
style |
Formatting, whitespace, lint — no logic change |
chore |
Build scripts, deps, tooling, config |
ci |
CI/CD pipeline changes |
revert |
Reverts a previous commit |
Output a classification table immediately:
| File | Status | Type | Scope | Brief description |
|---|---|---|---|---|
path/to/file.ts |
staged/unstaged | feat |
auth |
Added login form |
path/to/other.ts |
unstaged | chore |
deps |
Updated lockfile |
Do not proceed to Step 4 until this table is shown to the user.
Step 4 — Group into logical commit units
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 · 187 lines · 73 tokens per session scan A 6db1fd3d646e
smart-commit is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,664 once invoked, about $0.0003 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-30.
Other skills, from other repositories
commit-messages
Write git commit messages and pull request titles in the WARP format used by the swarms repo.
adk-git
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a…
commit-context
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
potpie-graph
Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with graph catalog, read named views with graph read, resolve entity identity with graph search-entities, create validated plans with graph propose, commit plans with graph commit --verify, inspect quality with…