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/signalcompose/claude-tools/git-workflow-setupnpx skills add signalcompose/claude-tools --skill git-workflow-setupgit clone --depth 1 https://github.com/signalcompose/claude-toolsWhat 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.00071 | $0.00844 |
| Opus 5 | $0.00036 | $0.00422 |
| Sonnet 5 | $0.00014 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
git-workflow-setup 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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Setup
This skill configures a complete Git workflow for your project, including branch structure, branch protection, merge settings, and security configuration.
What This Skill Does
- Project Type Selection - Determine security level (Personal / Small OSS / Large OSS)
- Development Style Selection - Solo or Team development
- Repository Check - Verify or create GitHub repository
- Branch Structure - Create main and develop branches
- Branch Protection - Apply protection rules using templates
- Merge Settings - Disable squash/rebase merge (merge commit only for Git Flow)
- Security Settings - CODEOWNERS, Secret Scanning (based on project type)
- Verification - Confirm all settings are correct
Execution Steps
Step 0: Project Type & Development Style
Ask the user about their project type to determine appropriate security settings:
| Setting | Personal | Small OSS | Large OSS |
|---|---|---|---|
| Visibility | Private | Public | Public |
| Secret Scanning | Not needed | Recommended | Required |
| CODEOWNERS | Not needed | Recommended | Required |
| develop protection | Optional | Recommended | Required |
| Fork PR restriction | Not needed | Optional | Recommended |
Then ask development style:
- Solo Development -
enforce_admins=false(admin bypass allowed) - Team Development -
enforce_admins=true(all rules apply to everyone)
Step 1: Repository Check
git remote -v
gh repo view --json nameWithOwner,isPrivate,defaultBranchRef 2>/dev/null
If no repository exists, guide the user to create one first.
Step 2: Branch Structure
Create develop branch if it doesn't exist, push to remote, and verify the default branch.
Step 3: Branch Protection
Apply branch protection using the template files:
- Solo:
${CLAUDE_PLUGIN_ROOT}/templates/.github/branch-protection/solo-development.json - Team:
${CLAUDE_PLUGIN_ROOT}/templates/.github/branch-protection/team-development.json
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.
- 2d ago First seen · 106 lines · 71 tokens per session scan A 31c1b82e9d4a
git-workflow-setup is a skill published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. It adds 71 tokens to every session and 844 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.