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 cyperx84/claude-code-plugin-examples --skill git-workflow-guidegit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWrote 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/cyperx84/claude-code-plugin-examples/git-workflow-guide)<a href="https://agentmods.dev/skills/cyperx84/claude-code-plugin-examples/git-workflow-guide"><img src="https://agentmods.dev/badge/skills/cyperx84/claude-code-plugin-examples/git-workflow-guide/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/cyperx84/claude-code-plugin-examples/git-workflow-guide"><img src="https://agentmods.dev/badge/skills/cyperx84/claude-code-plugin-examples/git-workflow-guide.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.00021 | $0.02540 |
| Opus 5.5 | $0.00008 | $0.01016 |
| Sonnet 5.5 | $0.00004 | $0.00508 |
| Haiku 4.5 | $0.00002 | $0.00254 |
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 2mo 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Guide
Purpose
Provide comprehensive guidance on:
- Git branching strategies
- Collaboration workflows
- Merge vs rebase decisions
- Conflict resolution
- Git best practices
When to Use
Invoke this skill when:
- Setting up a new project's git workflow
- User asks about branching strategy
- Resolving merge conflicts
- Deciding between merge, rebase, or squash
- Onboarding team members to git practices
- Troubleshooting git issues
Instructions
Step 1: Understand the Context
Determine:
- Team size: Solo, small team (2-5), medium (6-20), large (20+)
- Release cadence: Continuous, weekly, monthly, versioned
- Collaboration style: Individual, pair programming, code review
- Project maturity: New, active development, maintenance mode
Step 2: Recommend Workflow
Choose appropriate workflow based on context:
For Solo Developers
- Simple trunk-based: Main branch + feature branches
- Minimal overhead
- Quick iterations
For Small Teams (2-5)
- GitHub Flow: Main + feature branches
- Pull requests for review
- Deploy from main
For Medium Teams (6-20)
- Git Flow: Main, develop, feature, release, hotfix branches
- Structured release process
- Clear separation of concerns
For Large Teams/Complex Projects
- Trunk-Based Development: Short-lived feature branches
- Feature flags for incomplete features
- Continuous integration focus
Step 3: Provide Specific Guidance
Based on the user's question, provide detailed guidance on:
- Branch naming conventions
- Commit strategies
- Merge/rebase best practices
- Code review process
- Release management
Branching Strategies
GitHub Flow (Recommended for Most)
Branches:
main: Always deployable, production codefeature/*: Short-lived feature branches
Workflow:
# 1. Create feature branch from main
git checkout main
git pull origin main
git checkout -b feature/user-authentication
# 2. Make changes and commit
git add .
git commit -m "feat(auth): add login functionality"
# 3. Push and create pull request
git push -u origin feature/user-authentication
# 4. After review, merge to main
# (Usually done via PR interface)
# 5. Delete feature branch
git branch -d feature/user-authentication
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.
- 2mo ago First seen · 487 lines · 21 tokens per session scan A 833d1adb3c29
Git Workflow Guide is a skill published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 1y ago), licensed MIT. It adds 21 tokens to every session and 2,540 once invoked, about $0.0001 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.