Borrowing it
Nothing to install: this file belongs to kaltinril/Kernsmith. 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/kaltinril/Kernsmith/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/kaltinril/KernsmithWrote 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/kaltinril/kernsmith/commit)<a href="https://agentmods.dev/skills/kaltinril/kernsmith/commit"><img src="https://agentmods.dev/badge/skills/kaltinril/kernsmith/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/kaltinril/kernsmith/commit"><img src="https://agentmods.dev/badge/skills/kaltinril/kernsmith/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 73 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 73 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00077 | $0.01200 |
| Opus 5.5 | $0.00031 | $0.00480 |
| Sonnet 5.5 | $0.00015 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Automate the full git commit workflow in one shot. No user intervention needed between steps unless something looks wrong.
Important
Run all git commands directly (e.g., git status) without prefixing cd <path> &&. The Bash tool already runs in the project's working directory, and the cd prefix breaks permission allow-list matching on Bash(git *).
Steps
1. Gather context (run all three in parallel)
git status # overview of staged, unstaged, untracked (NEVER use -uall)
git diff --stat # summary of staged + unstaged changes
git log --oneline -5 # recent messages for style matching
2. Check for phase doc updates
Before drafting the commit message, scan the diff for changes that should be reflected in project docs. If changes touch phase deliverables (new API methods, schema changes, parser updates, etc.), check whether plan/master-plan.md or the relevant plan/phase-*.md file needs updating. If so, make those edits and include them in the commit. Don't create a separate commit for doc updates — bundle them together.
2b. Update phase document status
If the changes being committed implement work from a specific phase, update the phase's status in both the phase document and the master plan. This keeps the project's planning docs in sync with reality.
How to determine which phase is affected:
- Look at the files being changed and match them to phase deliverables
- Check commit message context (e.g., "Phase 55" in the message or branch name)
- If unsure, skip this step — only update when you're confident
What to update in the phase doc (plan/phase-*.md):
- Update the
> **Status**:line in the header (e.g.,Planning→In Progress,In Progress→Complete, orPlanning→Partialif only some items were done)
What to update in plan/master-plan.md:
- Update the status column in the Active Plans table to match
- Update the phase heading in the Phased Implementation section (e.g.,
(PLANNING)→(IN PROGRESS)or(COMPLETE))
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 · 101 lines · 77 tokens per session scan A 486bbcfd7d6a
commit is a skill published in the GitHub repository kaltinril/Kernsmith (11 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,200 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-09-04.
Other skills, from other repositories
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
sentry
Use when adding error tracking, performance monitoring or release health to .NET apps — builder.WebHost.UseSentry, SetBeforeSend, SentrySdk.CaptureException, TracesSampleRate, StartTransaction/StartChild spans, Source Context, symbol upload. Also for events not arriving because Dsn is empty (the SDK stays silent)…
safe-github-push
A workflow for safely pushing Git repositories that contain large assets or binary files to GitHub. It checks repository changes and file sizes before planning commits and pushes.
asp-commit
Git commit + push of current-session changes only, in one Bash chain. Use when the user asks to commit or push.
cratis-commits-and-pull-requests
Use before writing commit messages, staging, pushing or creating and editing PRs, including release labels and issue references. Not for candidate assembly, issue status or batching release windows.