Borrowing it
Nothing to install: this file belongs to spytensor/openmozi. 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/spytensor/openmozi/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/spytensor/openmoziWrote 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/spytensor/openmozi/commit)<a href="https://agentmods.dev/skills/spytensor/openmozi/commit"><img src="https://agentmods.dev/badge/skills/spytensor/openmozi/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/spytensor/openmozi/commit"><img src="https://agentmods.dev/badge/skills/spytensor/openmozi/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.00035 | $0.00521 |
| Opus 5.5 | $0.00014 | $0.00208 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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 2mo 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.
What it actually says
Smart Commit
When the user asks to commit, execute ALL of these steps:
Step 1: Analyze Changes
git status
git diff --stat
git diff
git log --oneline -5
Understand what was changed and why.
Step 2: Determine Version Bump
Read package.json to get the current version. Determine the bump type based on changes:
- patch (x.y.Z): bug fixes, minor tweaks
- minor (x.Y.0): new features, new commands, new modules
- major (X.0.0): breaking changes
Update the "version" field in package.json.
Step 3: Find Related Issues
Check if there are open GitHub issues related to the changes:
gh issue list --state open --limit 20
Match the changes against issue titles/descriptions. If a related issue is found, reference it in the commit message as (#N) and close it after pushing.
If $ARGUMENTS contains an issue number, use that directly.
Step 4: Build & Test
pnpm build
pnpm test
If either fails, fix the issues before committing. Do NOT commit broken code.
Step 5: Commit
Stage the changed files (be specific, avoid git add -A for safety):
git add <specific files>
git commit -m "<type>: <description> (#<issue>)
Co-authored-by: Mozi <[email protected]>"
Commit type: feat: for features, fix: for bugs, refactor: for refactors, chore: for config/deps.
Step 6: Push
git push origin main
Step 7: Close Related Issues
If a related issue was found:
gh issue close <N> --comment "Implemented in <commit-hash> (v<new-version>)."
Step 8: Report
Print a summary:
- Version: old -> new
- Commit: hash
- Files changed: count
- Issue closed: #N (if any)
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.
- 2mo ago First seen · 87 lines · 35 tokens per session scan A 3f590ee1b970
commit is a skill published in the GitHub repository spytensor/openmozi (441 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 521 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-30.
commit compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| commitspytensor/openmozi | Skill | 441 | 3mo ago | MIT | A | 35 | Claude Code |
| github-pr-workflowStarryCod/cogitum | Skill | 12 | 5mo ago | MIT | D | 20 | Claude Code, Codex |
| caveman-commitJuliusBrussee/caveman | Skill | 118k | yesterday | Apache-2.0 | A | 38 | Claude Code |
| baby-sitlangchain-ai/open-swe | Skill | 11k | yesterday | MIT | A | 30 | Claude Code, Codex |
| meta-pre-commit-quality-gateopensquilla/opensquilla | Skill | 7.1k | 6d ago | Apache-2.0 | A | 68 | Claude Code, Codex |
| commitopenonion/connectonion | Skill | 1.5k | yesterday | Apache-2.0 | A | 26 | Claude Code, Codex |
| app_tagline_backfillrome-os/rome | Skill | 889 | yesterday | MIT | A | 0 | Claude Code, Codex |