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/duyet/oma/git-commitnpx skills add duyet/oma --skill git-commitgit clone --depth 1 https://github.com/duyet/omaWhat 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.00075 | $0.00808 |
| Opus 5 | $0.00037 | $0.00404 |
| Sonnet 5 | $0.00015 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-commit
Good commits are small, atomic, and self-describing: one logical change per commit, a message that says what changed and why. Do not push unless the user asks.
Before committing
git statusandgit diff— know exactly what you're about to record.- Stage deliberately.
git add <specific paths>for the change you're describing. Avoidgit add -Awhen the working tree has unrelated edits. - Don't commit junk: secrets/tokens,
.envfiles, build output,node_modules, editor cruft, large binaries, debugconsole.log/print. If something shouldn't be tracked, add it to.gitignoreinstead. - Not on the default branch. If you're on
main/masterand this isn't a trivial fixup the user asked for, create a branch first.
Conventional Commits format
<type>(<scope>): <summary>
<body — why, not just what>
<footer — refs, BREAKING CHANGE>
- type:
feat·fix·docs·refactor·test·chore·perf·build·ci·style·revert. - scope: the area touched (
auth,api,parser, …) — keep it consistent with scopes already used ingit log. - summary: imperative mood, lowercase, no trailing period, <= ~72 chars ("add retry to fetch", not "added" / "adds" / "Added.").
- body (optional): wrap ~72 cols, explain the reasoning and any tradeoff — the diff already shows what.
- breaking change: footer
BREAKING CHANGE: …(ortype!:in the header).
Examples:
feat(agent): add exponential backoff to model retries
fix(session): stop dropping events when the DO restarts mid-turn
docs(readme): document the seed-skills workflow
Small and atomic
- One concern per commit. If you did two unrelated things, make two commits
(
git add -pto split a mixed working tree by hunk). - A commit should leave the tree in a working state — don't commit code that doesn't build if you can help it.
- Prefer several focused commits over one giant "misc changes" blob. Reviewers
and
git bisectboth benefit.
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 · 74 lines · 75 tokens per session scan A 2a8b965edafa
git-commit is a skill published in the GitHub repository duyet/oma (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 75 tokens to every session and 808 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…