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 zircote-plugins/sdlc-quality --skill vcsgit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWrote 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/zircote-plugins/sdlc-quality/vcs)<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/vcs"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/vcs/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/zircote-plugins/sdlc-quality/vcs"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/vcs.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.00067 | $0.01493 |
| Opus 5.5 | $0.00027 | $0.00597 |
| Sonnet 5.5 | $0.00013 | $0.00299 |
| Haiku 4.5 | $0.00007 | $0.00149 |
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 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 — 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
ghplugin provides Git workflow commands (/gh:commit,/gh:pr,/gh:sync). Thecommit-commandsplugin 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 |
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 · 271 lines · 67 tokens per session scan A 06ddc59e8949
vcs is a skill published in the GitHub repository zircote-plugins/sdlc-quality (11 stars, last pushed 29d ago), licensed MIT. It adds 67 tokens to every session and 1,493 once invoked, about $0.0003 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
cut-release
Cut a clean release — bump versions across all files, update changelog, create GitHub release.
merge-to-main
Babysit a PR through CI — create, monitor, fix failures, merge when green.
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
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…
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).