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/carlosroman/yet-another-mcp-server/git-commitnpx skills add carlosroman/yet-another-MCP-server --skill git-commitgit clone --depth 1 https://github.com/carlosroman/yet-another-MCP-serverWhat 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.00017 | $0.00412 |
| Opus 5 | $0.00009 | $0.00206 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
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.
What it actually says
What I do
- Analyze staged changes to determine commit type and scope
- Generate conventional commit messages in standard format
- Auto-commit without prompting
When to use me
Run when you have staged changes ready to commit. I'll auto-detect the appropriate type and scope based on the changes and your prompt context.
Workflow
- Check for staged changes (
git diff --staged --name-only) - If empty: error with
git add <files>suggestion and exit - Auto-detect type using prompt context and file analysis:
- CI configs (
.github/,.gitlab-ci.yml) →ci - Build configs (
pyproject.toml,uv.lock) →build - Performance improvements →
perf(when mentioned in prompt) - Test files →
test, Documentation →docs - Source code: infer from changes (new API →
feat, bug fix →fix, restructuring →refactor) - Config/maintenance →
chore - If unclear: default to
featfor new,fixfor modified
- CI configs (
- Auto-detect scope from
src/yams/<folder>(tools, transport, config, server) - Generate message:
- Subject: imperative, ≤50 chars, no period
- Body: 1-3 bullet points explaining key changes
- Check for
BREAKING CHANGEmarker in diff
- Execute:
git commit -m "<message>"
Example output
feat(tools): add git-commit skill for conventional commits
- Create SKILL.md with frontmatter and workflow
- Implement auto-detection for type and scope
Edge cases
- No staged changes: error with
git addsuggestion - Mixed file types: use primary type or
chore
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 · 43 lines · 17 tokens per session scan A 917aa381d1d3
git-commit is a skill published in the GitHub repository carlosroman/yet-another-MCP-server (0 stars, last pushed 24d ago), licensed MIT. It adds 17 tokens to every session and 412 once invoked, about $0.0001 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…