Borrowing it
Nothing to install: this file belongs to edochi/mdvs. 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/edochi/mdvs/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/edochi/mdvsWrote 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/edochi/mdvs/commit)<a href="https://agentmods.dev/skills/edochi/mdvs/commit"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/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/edochi/mdvs/commit"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/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.00038 | $0.00566 |
| Opus 5.5 | $0.00015 | $0.00226 |
| Sonnet 5.5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00057 |
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 10d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit & Branching Conventions
Branching
Never push directly to main. All work goes through feature branches + PRs.
- One branch per TODO or feature:
feat/description,fix/description,docs/description - Branch off
main:git checkout -b feat/my-feature main - Always ask the user before creating a branch
- Merge via PR (regular merge, not squash)
When to Commit
Never commit unless the user explicitly asks. No autonomous commits. Wait for "commit", "commit and push", or similar.
Before Committing
- If the work corresponds to a spec TODO, update its status to
donebefore committing (use thetodoskill). This lets the user review the TODO update as part of the same diff. - Verify tests pass, clippy is clean, and fmt is applied.
Commit Workflow
Run git add, git commit, and git push as separate commands — never
chained together.
Staging
- Stage specific files by name — never use
git add -Aorgit add . - Don't stage files that contain secrets (
.env, credentials)
Commit Messages
Use Conventional Commits format. A
commit-msg hook (cocogitto) enforces this.
Format: <type>[optional scope]: <description>
Types: feat, fix, refactor, docs, test, chore, ci, perf, style
git commit -m "$(cat <<'EOF'
feat: add enum constraints on string fields
EOF
)"
Push
Only push when the user explicitly asks. "Commit" does not imply "push". Wait for "push", "commit and push", or similar.
Pull Requests
After pushing a feature branch, create a PR to main when the user asks. Use
gh pr create with a clear title and summary. CI must pass before merging. Use
regular merge (not squash).
Safety Rules
- Never push directly to
main - Never amend, force-push, or skip hooks — unless the user explicitly asks
- Never rebase interactively (
git rebase -i) - If a pre-commit hook fails, fix the issue and create a new commit (don't amend)
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.
- 10d ago First seen · 74 lines · 38 tokens per session scan A d0af903a616b
commit is a skill published in the GitHub repository edochi/mdvs (27 stars, last pushed 11d ago), licensed MIT. It adds 38 tokens to every session and 566 once invoked, about $0.0002 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-10-05.
Other skills, from other repositories
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
ship
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'.…
git
Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…
cocosearch-commit
Use when committing changes — analyzes staged (or unstaged) diffs with CocoSearch semantic search and dependency impact to generate comprehensive Conventional Commit messages. Reviews changes thoroughly, then asks user to approve, edit, or abort the commit.