Borrowing it
Nothing to install: this file belongs to AlphaLab-USTC/OhMyCode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AlphaLab-USTC/OhMyCode/main/.agents/skills/commit-conventions/SKILL.mdgit clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCodeWrote 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/alphalab-ustc/ohmycode/commit-conventions)<a href="https://agentmods.dev/skills/alphalab-ustc/ohmycode/commit-conventions"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/commit-conventions/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/alphalab-ustc/ohmycode/commit-conventions"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/commit-conventions.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.00030 | $0.00503 |
| Opus 5.5 | $0.00012 | $0.00201 |
| Sonnet 5.5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
commit-conventions 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.
What it actually says
OhMyCode Commit Conventions
Format
<type>(<scope>): <description>
All lowercase. Description should be imperative mood ("add", not "adds" or "added").
Types
| Type | When to Use |
|---|---|
feat |
New feature or capability |
fix |
Bug fix |
docs |
Documentation only |
test |
Adding or updating tests |
refactor |
Code change that neither fixes a bug nor adds a feature |
chore |
Build, tooling, dependency changes |
style |
Formatting, whitespace (no logic change) |
Scope Inference
Infer scope from the primary file path changed:
| Path Pattern | Scope |
|---|---|
ohmycode/tools/* |
tools |
ohmycode/core/* |
core |
ohmycode/providers/* |
providers |
ohmycode/config/* |
config |
ohmycode/memory/* |
memory |
ohmycode/storage/* |
storage |
ohmycode/cli.py |
cli |
tests/* |
same as the source being tested |
docs/* |
omit scope |
.claude/skills/* or .agents/skills/* |
skills |
If changes span multiple scopes, use the primary one or omit scope.
Examples
feat(tools): add sql_query tool
fix(providers): handle empty delta in OpenAI streaming
docs: update DEVELOPMENT_GUIDE with hook system
test(core): add permission rule matching edge cases
refactor(cli): extract render_stream into separate module
chore: bump openai dependency to 1.52.0
feat(skills): add debug-ohmycode skill
Rules
- First line under 72 characters
- No period at the end
- Body is optional — add if the change needs explanation
- Reference issue numbers if applicable:
fix(core): handle empty messages (#42) - Breaking changes: add
!after scope:feat(config)!: change rules format
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 First seen · 66 lines · 30 tokens per session scan A 3be62dbc8b86
commit-conventions is a skill published in the GitHub repository AlphaLab-USTC/OhMyCode (132 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 503 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…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.