Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ValorVie/custom-skillsnpx agentmods add skills/valorvie/custom-skills/git-workflow-guideWrote 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/valorvie/custom-skills/git-workflow-guide)<a href="https://agentmods.dev/skills/valorvie/custom-skills/git-workflow-guide"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/git-workflow-guide.svg" alt="Measured on agentmods" 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.00060 | $0.01683 |
| Opus 5 | $0.00030 | $0.00842 |
| Sonnet 5 | $0.00012 | $0.00337 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
git-workflow-guide 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 5d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Guide
Language: English | 繁體中文
Version: 1.0.0 Last Updated: 2025-12-24 Applicability: Claude Code Skills
Core Standard: This skill implements Git Workflow. For comprehensive methodology documentation, refer to the core standard.
Purpose
This skill provides guidance on Git branching strategies, branch naming conventions, and merge operations.
Quick Reference
Workflow Strategy Selection
| Deployment Frequency | Recommended Strategy |
|---|---|
| Multiple times/day | Trunk-Based Development |
| Weekly to bi-weekly | GitHub Flow |
| Monthly or longer | GitFlow |
Branch Naming Convention
<type>/<short-description>
| Type | Usage | Example |
|---|---|---|
feature/ |
New functionality | feature/oauth-login |
fix/ or bugfix/ |
Bug fixes | fix/memory-leak |
hotfix/ |
Urgent production fixes | hotfix/security-patch |
refactor/ |
Code refactoring | refactor/extract-service |
docs/ |
Documentation only | docs/api-reference |
test/ |
Test additions | test/integration-tests |
chore/ |
Maintenance tasks | chore/update-dependencies |
release/ |
Release preparation | release/v1.2.0 |
Naming Rules
- Use lowercase
- Use hyphens for spaces
- Be descriptive but concise
Detailed Guidelines
For complete standards, see:
AI-Optimized Format (Token-Efficient)
For AI assistants, use the YAML format files for reduced token usage:
- Base standard:
ai/standards/git-workflow.ai.yaml - Workflow options:
- GitHub Flow:
ai/options/git-workflow/github-flow.ai.yaml - GitFlow:
ai/options/git-workflow/gitflow.ai.yaml - Trunk-Based:
ai/options/git-workflow/trunk-based.ai.yaml
- GitHub Flow:
- Merge strategy options:
- Squash Merge:
ai/options/git-workflow/squash-merge.ai.yaml - Merge Commit:
ai/options/git-workflow/merge-commit.ai.yaml - Rebase + FF:
ai/options/git-workflow/rebase-ff.ai.yaml
- Squash Merge:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 241 lines · 60 tokens per session scan A 11f501083428
git-workflow-guide is a skill published in the GitHub repository ValorVie/custom-skills (5 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 1,683 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-09-03.
Other skills, from other repositories
git-workflow
Branching, committing, PR creation, merge strategies, and git history management.
github-issues
Manage GitHub issues, pull requests, CI runs, and repository operations via the gh CLI.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.