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 sefaertunc/Worclaude --skill git-conventionsgit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/sefaertunc/worclaude/git-conventions)<a href="https://agentmods.dev/skills/sefaertunc/worclaude/git-conventions"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/git-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/sefaertunc/worclaude/git-conventions"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/git-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.00017 | $0.01966 |
| Opus 5.5 | $0.00007 | $0.00786 |
| Sonnet 5.5 | $0.00003 | $0.00393 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
git-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.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Conventions
Invocation Boundary
git commit, git push, and gh pr create are invoked only when the human
explicitly types /commit-push-pr or /sync (or one of their listed Trigger
Phrases). The slash commands themselves are not invoked autonomously — wait for
the human trigger. The Version bump: AskUserQuestion in /commit-push-pr is
non-skippable; refuse to proceed without an explicit human selection.
See CLAUDE.md Critical Rule 13.
Branch Naming
Pattern: {type}/{short-description}
Types:
feature/— New functionalityfix/— Bug fixesrefactor/— Code restructuring without behavior changedocs/— Documentation onlytest/— Test additions or fixeschore/— Tooling, dependencies, config
Examples:
feature/auth-flowfix/login-timeoutrefactor/extract-merger-module
Keep branch names under 50 characters. Use hyphens, not underscores.
Commit Messages
Follow conventional commits format:
type(scope): short description
Longer explanation if needed. Focus on WHY, not WHAT.
The diff already shows what changed.
Closes #123
Types: feat, fix, refactor, test, docs, chore, perf, ci
Scope is optional but helpful: feat(auth): add OAuth2 token refresh
Rules:
- Subject line under 72 characters
- Imperative mood ("add" not "added" or "adds")
- No period at the end of the subject line
- Blank line between subject and body
- Body explains motivation, not mechanics
- Never append Co-Authored-By trailers, AI attribution lines, or "Generated with" footers
When to Commit
Commit after each logical unit of work:
- A function is complete and tested
- A refactor is done and tests pass
- A bug is fixed and verified
Don't batch unrelated changes into one commit. Don't commit broken code.
Branching Strategy
feature-branch ──PR──▶ develop ──PR──▶ main (release)
develop— active development. Contributors fork, branch fromdevelop, and PR back todevelop.main— production releases. Maintainer-only, merged fromdevelop.gh-pages— auto-deployed docs. Maintainer-only.
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 · 206 lines · 17 tokens per session scan A 69823656b086
git-conventions is a skill published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,966 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-31.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
git-ops
Git + worktree orchestrator: status survey, per-worktree triage, commits, PRs, branches, releases, rebases — reads inline, writes to a background agent. Triggers on: git status, anything to commit, anything to push, commit, push, create PR, rebase, release, tag, changelog, worktree, land worktrees.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
git-workflow-and-versioning
Manage branches, commits, conflicts, semantic versions, and changelogs when preparing Git changes or releases.