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 agentmods add skills/khanh-vu/claude-force/git-workflownpx skills add khanh-vu/claude-force --skill git-workflowgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/git-workflow)<a href="https://agentmods.dev/skills/khanh-vu/claude-force/git-workflow"><img src="https://agentmods.dev/badge/skills/khanh-vu/claude-force/git-workflow.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 | $0.00000 | $0.03427 |
| Opus 5 | $0.00000 | $0.01714 |
| Sonnet 5 | $0.00000 | $0.00685 |
| Haiku 4.5 | $0.00000 | $0.00343 |
Grade A, and why
git-workflow 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 4d 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 — 744 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Skill
Overview
Best practices and patterns for Git workflows, commit conventions, branching strategies, and collaborative development.
Capabilities
- Commit message conventions
- Branching strategies
- Pull request workflows
- Git best practices
- Conflict resolution
- Code review integration
Commit Message Conventions
Format
<type>(<scope>): <subject>
<body>
<footer>
Types
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, missing semicolons, etc. (no code change)
- refactor: Code change that neither fixes a bug nor adds a feature
- perf: Performance improvement
- test: Adding or updating tests
- chore: Changes to build process or auxiliary tools
- ci: Changes to CI configuration files and scripts
- revert: Reverts a previous commit
Examples
# Feature
git commit -m "feat(auth): add JWT authentication
Implemented JWT-based authentication with refresh tokens.
Added middleware for protected routes.
Closes #123"
# Bug fix
git commit -m "fix(api): resolve race condition in order processing
Added transaction locking to prevent duplicate orders.
Fixes #456"
# Documentation
git commit -m "docs(readme): update installation instructions
Added Docker setup instructions and troubleshooting section."
# Refactor
git commit -m "refactor(users): extract validation logic to separate module
Moved user validation functions to utils/validators.js
for better reusability and testing."
# Performance
git commit -m "perf(database): optimize user query with indexes
Added composite index on (email, status) for 10x query speedup.
Benchmark results:
- Before: 500ms avg
- After: 50ms avg"
# Test
git commit -m "test(auth): add integration tests for login flow
Added tests for successful login, failed login, and token refresh."
# Breaking change
git commit -m "feat(api)!: change user API response format
BREAKING CHANGE: User API now returns snake_case instead of camelCase.
Migration guide in docs/migrations/v2.md
Closes #789"
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.
- 4d ago First seen · 744 lines · 0 tokens per session scan A 02bb6e2c50a5
git-workflow is a skill published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,427 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…