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 skills add wufunc/nova --skill git-commitgit clone --depth 1 https://github.com/wufunc/novaWrote 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/wufunc/nova/git-commit)<a href="https://agentmods.dev/skills/wufunc/nova/git-commit"><img src="https://agentmods.dev/badge/skills/wufunc/nova/git-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/wufunc/nova/git-commit"><img src="https://agentmods.dev/badge/skills/wufunc/nova/git-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.00087 | $0.01411 |
| Opus 5.5 | $0.00035 | $0.00564 |
| Sonnet 5.5 | $0.00017 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
git-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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Overview
This skill automates the complete git commit workflow: analyze changes,
generate an English Conventional Commit message in the required
<type>: AI <subject> format, update project memory, stage, commit,
and tag.
Workflow
Execute the following steps in order when this skill is invoked:
Step 1: Analyze Conversation Context
Review the conversation history to understand:
- What code changes were made
- What features were added or bugs were fixed
- What architectural decisions or design choices were discussed
- What files were modified or created
Step 2: Check Git Status
Run parallel git commands to gather current repository state:
# Check untracked and modified files (never use -uall flag)
git status
# View staged and unstaged changes
git diff HEAD
# View recent commit messages to understand the project's commit style
git log --oneline -10
Step 3: Generate Commit Message
Based on the analysis, generate a commit message following Conventional Commits format.
Format:
<type>: AI <subject>
<body>
Co-Authored-By: AI Coding Agent <[email protected]>
Type options:
build: Build system or dependencies changeschore: Maintenance work that does not fit other typesci: CI/CD changesdocs: Documentation changesfeat: New featurefix: Bug fixperf: Performance improvementsrefactor: Code refactoring without behavior changerevert: Revert a previous changestyle: Formatting or style-only changes with no logic impacttest: Adding or updating tests
Guidelines:
- Always use one of the allowed types above; do not invent new types
- Do not add a scope; the prefix must stay exactly
<type>: AI - Subject: Concise summary (50-72 chars max), imperative mood, no period, written in English
- Body: When needed, explain what changed and why in English, including key implementation details and impact on the codebase
- Keep each line in body under 72 characters
- Use blank line between subject and body
- Example:
feat: AI user login
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 · 162 lines · 87 tokens per session scan A e8e182a26d99
git-commit is a skill published in the GitHub repository wufunc/nova (2 stars, last pushed 6mo ago), licensed MIT. It adds 87 tokens to every session and 1,411 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.