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/kraitdev/skill.md/git-workflow-branchingnpx skills add KraitDev/skiLL.Md --skill git-workflow-branchinggit clone --depth 1 https://github.com/KraitDev/skiLL.MdWhat 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.00022 | $0.01465 |
| Opus 5 | $0.00011 | $0.00732 |
| Sonnet 5 | $0.00004 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
git-workflow-branching 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 yesterday.
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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow & Branching
Purpose
Clean git history is essential for debugging (git bisect), code review, and team collaboration. This skill standardizes branch naming, commit formatting, and merging to maintain a readable, revertible, and bisect-able history.
When to use
- Starting a new feature or bugfix ticket
- Reviewing PRs and merging code into mainline
- Hotfixing production environments
- Onboarding new team members
When NOT to use
- Dealing with complex merge conflicts (use git documentation)
- Repository history rewrites (different concern)
- CI/CD trigger configuration (separate skill)
Inputs required
- Git repository with
mainbranch - Remote repository (GitHub, GitLab, Gitea)
- Team agreement on branch naming and commit conventions
Workflow
- Sync Main: ALWAYS fetch and pull latest from
mainbefore creating branch - Create Branch: Use convention
type/ticket-id-short-description(e.g.,feat/PROJ-123-add-login) - Commit Atomically: Commit in small logical chunks. MUST use Conventional Commits format
- Keep Branch Synced: Rebase against
mainfrequently to avoid merge conflicts - Push Regularly: Push to remote regularly (enables collaboration, backup)
- Rebase Before PR: Interactive rebase to clean up WIP commits before opening PR
- Squash Merge: Merge PR using squash-merge to keep main history clean
- Delete Branch: Delete feature branch after merging (cleanup)
Rules
- MUST NEVER push directly to
main(always use PRs) - MUST use Conventional Commits:
feat:,fix:,docs:,chore:,refactor:,test: - MUST rebase before opening PR (no merge commits from main)
- MUST delete feature branches after merging
- MUST NOT commit with messages like "wip", "fixed typo", "trying again"
- MUST resolve conflicts locally before pushing
- MUST NOT force-push to shared branches
- MUST keep feature branches <5 days old before merging
Anti-patterns
- WIP Commits: Pushing commits like "wip", "fixed typo", "let me try again" to main
- Long-lived Branches: Keeping branches active for weeks without syncing with main
- Merge Commits: Allowing merge commits from main to pollute history (use rebase)
- Squashing Too Early: Squashing before PR review (makes feedback hard to track)
- Force Pushing to Shared:
git push -fon branches other developers are using - Vague Messages: "Update stuff", "fix bug" (impossible to bisect later)
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.
- yesterday First seen · 151 lines · 22 tokens per session scan A b221525d9b5f
git-workflow-branching is a skill published in the GitHub repository KraitDev/skiLL.Md (7 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,465 once invoked, about $0.0001 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.
Other skills, from other repositories
evaluate-pattern-adoption
Run or plan this repository's pattern-adoption evidence evaluation locally with signed-in Codex agents. Use when asked to refresh stale evidence, assess stable or exploratory patterns, evaluate one or all catalog patterns, discover possible new patterns, or prepare a reviewable evidence PR without model-backed GitHub…
contributing-to-awesome-claude
Use when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts). The…
react-artifact
Author app-like designs in React/JSX and bundle them in-sandbox into the same single self-contained HTML artifact Design Studio delivers. Use when the design needs real state, complex interactivity, or component reuse beyond what vanilla JS comfortably handles.
contributor-pipeline-gardening
Maintenance of the contributor issue pipeline for JSONbored/awesome-claude (HeyClaude) — closing issues that are already done but not marked so, and keeping a small, high-value contributor-available backlog stocked with real website/content/feature/bugfix work. Runs every 24h via a dedicated scheduled task. Invoke for…
Ticket Specs
Create, regenerate, update, and review Xyne Spaces ticket Specifications by interviewing for requirement intent before drafting or writing the Specification.
explanation-document
Structure a codebase/schema explanation as a self-contained HTML document ordered for a READER — mental model and flows first, deep per-component reference last — not in the order you explored it.