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/wufunc/nova/git-commitnpx skills add wufunc/nova --skill git-commitgit clone --depth 1 https://github.com/wufunc/novaWhat 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.00087 | $0.01411 |
| Opus 5 | $0.00044 | $0.00705 |
| Sonnet 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 yesterday.
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.
- yesterday 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 4mo ago), licensed MIT. It adds 87 tokens to every session and 1,411 once invoked, about $0.0004 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
telnyx-ai-inference-curl
Access Telnyx LLM inference APIs, embeddings, and AI analytics for call insights and summaries. This skill provides REST API (curl) examples.
telnyx-ai-assistants-go
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
telnyx-email-inbound-curl
Manage email inboxes, list and search inbound messages, threads, sender filters, and reply to or forward messages. Use for building email agents that read and respond to incoming email.
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.
telnyx-numbers-compliance-curl
Manage regulatory requirements, number bundles, supporting documents, and verified numbers for compliance. This skill provides REST API (curl) examples.
telnyx-numbers-config-curl
Configure phone number settings including caller ID, call forwarding, messaging enablement, and connection assignments. This skill provides REST API (curl) examples.