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/myths-labs/muse/git-commitnpx skills add myths-labs/muse --skill git-commitgit clone --depth 1 https://github.com/myths-labs/museWhat 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.00063 | $0.01663 |
| Opus 5 | $0.00032 | $0.00831 |
| Sonnet 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 2d 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.
- 2d 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 (32 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,663 once invoked, about $0.0003 per session on Opus 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
project-brain
Triggers (all require explicit user request — do NOT activate just because a brain/ folder exists): (1) The user wants to set up project-level memory ("set up project brain", "scaffold project context", "init project brain", "建项目脑"). (2) The user is in a directory containing brain/ AND explicitly asks to resume /…
engram
Local-first personal AI identity and memory layer for MCP-compatible coding tools (Claude Code, Codex, Cursor, and others). Use this skill when the user wants to continue from a previous session ("continue from last session", "pick up where we left off"), recall a past decision ("what did we decide", "what was our…
context-receipts
Emit privacy-safe receipts for context selection, deferral, hydration, compaction, pruning, delegation, usage attribution, and boundary handoffs.
evidence-attestation
Emit privacy-safe evidence attestations for agent actions, reviews, memory answers, handoffs, scores, approvals, and tool dispatches.
skill-policy-receipts
Use when a task must obey a hard project policy, such as "do not generate tests for internal services", "do not call production APIs", or "do not edit generated files". Emits a privacy-safe receipt before writes and after guard checks.
testsprite-verify
TestSprite verification loop — after finishing a feature or fix in a TestSprite-tested repo, use the testsprite CLI to run the relevant TestSprite tests against the change and inspect any failure artifacts before reporting the work as done. Use whenever code has changed outside docs/config and is about to be reported…