Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add signalcompose/claude-tools/plugin install ypmWrote 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/signalcompose/claude-tools/git-workflow-setup)<a href="https://agentmods.dev/skills/signalcompose/claude-tools/git-workflow-setup"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/git-workflow-setup/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/signalcompose/claude-tools/git-workflow-setup"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/git-workflow-setup.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.00071 | $0.00844 |
| Opus 5.5 | $0.00028 | $0.00338 |
| Sonnet 5.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 1mo 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.
- 1mo 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 1mo ago), licensed MIT. It adds 71 tokens to every session and 844 once invoked, about $0.0003 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.