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 EvovexAI/EvoFlow --skill git-batch-commitgit clone --depth 1 https://github.com/EvovexAI/EvoFlowWrote 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/evovexai/evoflow/git-batch-commit)<a href="https://agentmods.dev/skills/evovexai/evoflow/git-batch-commit"><img src="https://agentmods.dev/badge/skills/evovexai/evoflow/git-batch-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/evovexai/evoflow/git-batch-commit"><img src="https://agentmods.dev/badge/skills/evovexai/evoflow/git-batch-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.00160 | $0.02169 |
| Opus 5 | $0.00080 | $0.01085 |
| Sonnet 5 | $0.00032 | $0.00434 |
| Haiku 4.5 | $0.00016 | $0.00217 |
Grade A, and why
git-batch-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 today.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 233 lines · 160 tokens per session scan A 5db3c665f515
git-batch-commit is a skill published in the GitHub repository EvovexAI/EvoFlow (197 stars, last pushed today), with no licence file. It adds 160 tokens to every session and 2,169 once invoked, about $0.0008 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-09-13.
Other skills, from other repositories
lakefs-versioning
Use when lakeFS data versioning — Git-like branching for data lakes, atomic commits, time travel, CI/CD. Use when working with lakefs versioning.
git-workflow
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
implement-specs
Implement code changes from an existing specs/ /TECH.md, one Implementation Plan step per commit, and update the spec in the same PR whenever reality diverges. Use after write-tech-spec, or when the user points at an existing TECH.md and says "implement this".
guardian
A guide for deciding how to organize commits, branches, merges, and pull requests. A pull request is a proposed code change submitted for review before it is merged.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.