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 Abilityai/abilities --skill commitgit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/commit)<a href="https://agentmods.dev/skills/abilityai/abilities/commit"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/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/abilityai/abilities/commit"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/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.00023 | $0.01156 |
| Opus 5.5 | $0.00009 | $0.00462 |
| Sonnet 5.5 | $0.00005 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
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 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.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.commit vX.Y — recent: <summary>. Then proceed.
Stage changed skill files, write a commit message tied to the in-progress issue, and close the issue with a summary. The single action that closes the loop between a GitHub issue and a SKILL.md change.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | Current repo | Yes | Yes | Close the in-progress issue |
| Git working tree | ./ | Yes | Yes | Stage and commit skill files |
Prerequisites
ghCLI authenticated- Git repo with at least one commit (not bare)
- Work is in-progress (a claimed issue exists) — or nothing is claimed and you just want a checkpoint commit (see Step 1)
Process
Step 1: Find the In-Progress Issue
gh issue list --label "status:in-progress" --state open --json number,title,body,labels --limit 5
If an issue number was passed as $ARGUMENTS, use that instead.
If multiple in-progress issues, ask which one this commit closes.
No in-progress issue and no argument → checkpoint mode. Do not stop: stage the agent-state set — memory/ .claude/memory/ outputs/ .claude/skills/ CLAUDE.md template.yaml (whatever exists; never .env, .mcp.json, *.log, or anything credential-shaped) — compose the message from the diff (Update agent state: <what changed>), commit, and report the sha. Skip the issue close in Step 5. This keeps /commit usable as a plain save when the agent is not running the issue workflow.
Step 2: Check for Changes
git status --short
Surface all modified, added, or deleted files. Flag anything that is NOT a SKILL.md or agent configuration file (CLAUDE.md, template.yaml) — confirm the user wants to include it.
If there are no changes at all: report "Nothing to commit. Did /adjust-playbook or /create-playbook run yet?"
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 Changed · +3 lines aafb8b27b0b5
- 1mo ago First seen · 144 lines · 23 tokens per session scan A 26c2e98ce5cc
commit is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 1,156 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.