vcs

vcs is a skill for Claude Code, Codex from zircote-plugins/sdlc-quality. It costs 67 tokens per session (1,493 once invoked), scanned A, original, MIT.

A set of version-control rules for Git workflows, including branches, commit messages, hooks, merges, and pull requests. Version control records code changes so teams can review and combine them safely.

In plain words
What is it for?
Use it to define branching strategies, branch names, commit conventions, Git hooks, merge rules, pull-request requirements, and release workflows.
Why use it?
It gives contributors a shared process for naming branches, protecting important branches, reviewing changes, and preparing releases.

Skill for Claude CodeCodex

Part of the sdlc plugin — 10 skills, 5 commands, 4 agents, 1 hook shipped together

Install

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.

agentmods
npx agentmods add skills/zircote-plugins/sdlc-quality/vcs
Any agent
npx skills add zircote-plugins/sdlc-quality --skill vcs
Clone the repo
git clone --depth 1 https://github.com/zircote-plugins/sdlc-quality

Made for: Claude Code, Codex.

Or install sdlc, the plugin that ships this one along with the rest of its 10 skills, 5 commands, 4 agents, 1 hook.

Wrote 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.

agentmods badge for vcs

README.md
[![agentmods](https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/vcs.svg)](https://agentmods.dev/skills/zircote-plugins/sdlc-quality/vcs)
Your own site
<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/vcs"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/vcs.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,493 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.01493
Opus 5 $0.00034 $0.00746
Sonnet 5 $0.00013 $0.00299
Haiku 4.5 $0.00007 $0.00149

Measured 3d ago against content hash 06ddc59e8949, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vcs 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 3d 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.

.github/skills/vcs/SKILL.md · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Version Control Standards

Guidance for implementing version control requirements including branching strategies, commit conventions, and Git workflow configuration.

Tooling

Available Tools: If using Claude Code, the gh plugin provides Git workflow commands (/gh:commit, /gh:pr, /gh:sync). The commit-commands plugin offers commit automation (/commit, /commit-push-pr).

Branching Strategy

Branch Types (MUST)

Projects MUST use a defined branching strategy with these branch types:

Branch Type Naming Pattern Purpose
Main main Production-ready code
Development develop Integration branch
Feature feature/* New functionality
Bugfix bugfix/* Bug repairs
Hotfix hotfix/* Emergency production fixes
Release release/* Release preparation

Branch Protection (MUST)

Protected branches (main, develop) MUST require:

  • Pull request reviews before merge
  • Status checks passing
  • No direct commits
  • Linear history (recommended)

Branch Naming (MUST)

Branch names MUST follow the pattern: type/description-with-dashes

Good:

feature/user-authentication
bugfix/login-timeout-error
hotfix/security-patch-cve-2024
release/v2.1.0

Bad:

my-branch
fix
Feature_UserAuth

Commit Message Standards

Conventional Commits (MUST)

Projects MUST use Conventional Commits format:

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

Commit Types (MUST)

Type Purpose
feat New feature
fix Bug fix
docs Documentation only
style Formatting, no code change
refactor Code restructuring
perf Performance improvement
test Adding/updating tests
build Build system changes
ci CI configuration
chore Maintenance tasks

Read the full file on GitHub · 271 lines

Changes

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.

  1. 3d ago First seen · 271 lines · 67 tokens per session scan A 06ddc59e8949

Subscribe to this mod's changes

vcs is a skill published in the GitHub repository zircote-plugins/sdlc-quality (10 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,493 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

procoder

Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…

azrtydxb/procoder · 101 tokens

bestie-features

Add BestieTemplate features (AGENTS.md, changelog, dependabot, pre-commit, lint workflow, testitem runner) to a Julia package with the bestie CLI — no Julia needed. Use when asked to add one of these files/setups to a package, or to see what BestieTemplate can add.

JuliaBesties/BestieTemplate.jl · 71 tokens

megalinter-check

Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…

oxsecurity/megalinter · 96 tokens

pr-watch-fix

Watch the GitHub PR for the current branch, wait for CI to finish, and autonomously fix failing jobs by reading logs, editing sources, and pushing. Stops cleanly when stuck.

oxsecurity/megalinter · 43 tokens

prepare-release

Prepare a MegaLinter release — update CHANGELOG (prune empty sections, collapse linter versions, backfill PR numbers), run the release build, push commit and tag, and guide GitHub release creation.

oxsecurity/megalinter · 46 tokens

add-linter

Guided workflow for adding a new linter to MegaLinter. Use when a contributor needs to add support for a new linting tool.

oxsecurity/megalinter · 33 tokens