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 myths-labs/muse --skill git-commitgit clone --depth 1 https://github.com/myths-labs/museWrote 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/myths-labs/muse/git-commit)<a href="https://agentmods.dev/skills/myths-labs/muse/git-commit"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/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/myths-labs/muse/git-commit"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/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.00063 | $0.01663 |
| Opus 5.5 | $0.00025 | $0.00665 |
| Sonnet 5.5 | $0.00013 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade B, and why
git-commit scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/CLAUDE.md 2>/dev/null | grep -A 20 -i "commit" Copies of this mod
1 near-identical copy found in the catalogue:
- commit — 88% identical, 39 lines differ
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Creates git commits following Conventional Commits format with proper type, scope, and subject.
Quick Start
# 1. Check for project-specific commit conventions
cat .claude/CLAUDE.md 2>/dev/null | grep -A 20 -i "commit"
# 2. Stage changes
git add <files> # or: git add -A
# 3. Create commit (branch commit format)
git commit -m "type(scope): subject
Body explaining HOW and WHY.
Reference: Task X.Y, Req N"
Commit Types
Regular Branch Commits (During Development)
Format: type(scope): subject
| Type | Purpose |
|---|---|
feat |
New feature or functionality |
fix |
Bug fix or issue resolution |
refactor |
Code refactoring without behavior change |
perf |
Performance improvements |
test |
Test additions or modifications |
ci |
CI/CD configuration changes |
docs |
Documentation updates |
chore |
Maintenance, dependencies, tooling |
style |
Code formatting, linting (non-functional) |
security |
Security vulnerability fixes or hardening |
Scope (Required, kebab-case)
Examples: validation, auth, cookie-service, template, config, tests, api
Subject Line Rules
- Max 50 characters after colon
- Present tense imperative: add, implement, fix, improve, enhance, refactor, remove, prevent
- NO period at the end
- Specific and descriptive - state WHAT, not WHY
Core Workflow
1. Check Project Conventions
ALWAYS check first - project may override defaults:
cat .claude/CLAUDE.md 2>/dev/null | grep -A 30 -i "commit"
cat .kiro/steering/*.md 2>/dev/null | grep -A 20 -i "commit"
If project specifies different format, USE PROJECT FORMAT.
2. Review Changes
git status
git diff --staged # if already staged
git diff # if not staged
3. Stage Files
git add <specific-files> # preferred
# or
git add -A # all changes
NEVER commit:
.env,.env.local,.env.prod*,.env.vercel*,credentials.json, secrets.muse/,.agent/,.gemini/,memory/,convo/— internal files*.pem,*.p12,*.jks,*.key— private keys/certificates- Files containing
sk-,AIzaSy,gsk_,sk_test_,eyJhbG— API keys/JWT node_modules/,__pycache__/,.venv/- Large binary files without explicit approval
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 · 241 lines · 63 tokens per session scan B bc3075e6878f
git-commit is a skill published in the GitHub repository myths-labs/muse (37 stars, last pushed 22d ago), licensed MIT. It adds 63 tokens to every session and 1,663 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
managing-git
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.