What is workspace-git-branch-rule?

A rule for naming and interpreting Git branches in a repository. It explains the roles of main, feature/id/{Issue number}/{name}, and release/{version}/main branches.

Use it to choose a new branch name, understand an existing feature or release branch, or look up the GitHub issue linked by a feature branch name.

Consistent branch names show whether work is ongoing, tied to a tracked issue, or prepared for release. For feature branches, the issue number provides a path to the actual task details.

workspace-git-branch-rule — Skill by eaglesakura/agent-skills

Install

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.

Any agent

npx skills add eaglesakura/agent-skills --skill workspace-git-branch-rule

Clone the repo

git clone --depth 1 https://github.com/eaglesakura/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eaglesakura/agent-skills/workspace-git-branch-rule/github.svg)](https://agentmods.dev/skills/eaglesakura/agent-skills/workspace-git-branch-rule)

Your own site

<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/workspace-git-branch-rule"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/workspace-git-branch-rule/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/workspace-git-branch-rule"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/workspace-git-branch-rule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 173 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,103 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00173	$0.01103
Opus 5.5	$0.00069	$0.00441
Sonnet 5.5	$0.00035	$0.00221
Haiku 4.5	$0.00017	$0.00110

Measured 2mo ago against content hash 2623ccaed521, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workspace-git-branch-rule 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.

packages/ohitorisama/.apm/skills/workspace-git-branch-rule/SKILL.md · 89 lines

What it actually says