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 skills/avmnu-sng/sutra/commit-craftnpx skills add avmnu-sng/sutra --skill commit-craftgit clone --depth 1 https://github.com/avmnu-sng/sutraWrote 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/avmnu-sng/sutra/commit-craft)<a href="https://agentmods.dev/skills/avmnu-sng/sutra/commit-craft"><img src="https://agentmods.dev/badge/skills/avmnu-sng/sutra/commit-craft.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.01558 |
| Opus 5 | $0.00016 | $0.00779 |
| Sonnet 5 | $0.00006 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
commit-craft 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 3d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit craft
Write the message for the engineer who lands on this line six months from
now with git blame, no context, and a production incident. Describe the
codebase-observable change and why it exists. Strip everything that only
made sense inside the session that produced it.
When to use
- You are about to write or amend a commit message.
- You are deciding how to split a pile of changes into commits.
- You are structuring a branch (or a stack of dependent branches).
When not to use
- Trivial mechanical noise the reader will never blame (leave it, or fold it into the logical commit it belongs to).
Subject line
- Imperative mood, plain English, under ~72 characters. "Add retry to upload client", not "Added" or "Adding".
- If your project uses a commit convention (Conventional Commits
feat:/fix:/..., gitmoji, anarea:summary scope, or a ticket-key prefix), follow it consistently. Absent one, a plain imperative subject naming the symbols is enough. - Use
fix(scope):only when the scope is genuinely narrower than the files touched. If the fix spans the files it names, drop the scope -- a scope wider than reality misleads. - Name the codebase-observable delta and the symbols involved: the function, type, constant, or file. "fix(auth): reject empty token in verify_session", not "fix: bug in auth".
- Never cite line numbers. They rot on the next edit. Name the symbol instead; a symbol survives a reformat, a line number does not.
Body
- Lead with WHAT the commit ships, in plain prose. Open with a verb on the
delta: "Move
parse_headerstohttp/headers.rb.", "Raise the connection pool cap from 8 to 32.", "Delete the unusedLegacyEncoderpath." - Keep the WHY only when it is not obvious from the WHAT. Non-obvious
reasons worth a sentence:
- a constraint (an upstream API caps page size at 100).
- a correctness or compliance reason (values must be redacted before logging).
- dead-code removal (no caller since the v2 client shipped).
- an operational precondition (requires the new column to be backfilled first).
- Optionally name who depends on this and one short pointer to verify it: "Consumed by the image-upload endpoint; run the upload smoke suite."
- Keep the body wrapped and readable. One blank line between subject and body.
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.
- 3d ago First seen · 153 lines · 32 tokens per session scan A 524deb9e59ae
commit-craft is a skill published in the GitHub repository avmnu-sng/sutra (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,558 once invoked, about $0.0002 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 skills, from other repositories
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
chinese-commit-conventions
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit-push-pr
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.