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 eaglesakura/agent-skills --skill workspace-git-branch-rulegit clone --depth 1 https://github.com/eaglesakura/agent-skillsWrote 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/eaglesakura/agent-skills/workspace-git-branch-rule)<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.
<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>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 | $0.00086 | $0.00551 |
| Sonnet 5 | $0.00035 | $0.00221 |
| Haiku 4.5 | $0.00017 | $0.00110 |
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 9d 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.
What it actually says
Workspace / Git Branch Rule
ブランチ名から役割を読み取り、新規ブランチをこの慣習に合わせて付ける。
名前から作業内容を追うときは、feature の Issue 番号を手がかりに gh で Issue を取る。
いつ使うか
- 作業用／リリース用ブランチの名前を決める・検証するとき
- 既存ブランチ名から「何の作業か」を推測するとき（特に
feature/id/...） main/ feature / release の役割の違いを揃えるとき
いつ使わないか
- コミットメッセージの書き方だけ
- PR のタイトル／本文の起草だけ（ブランチ名解釈が必要な場合は併用可）
- 実装・レビュー・テストそのもの
- 破壊的 git 操作（force push 等）の許可判断そのもの
ブランチ種別
main
- 開発中の最新コードを置く幹線
- 各リポジトリは、常に
mainの最新を作業の起点とする
feature/id/{Issue番号}/{任意の名称}
- 作業用ブランチ。リポジトリの Issue に紐づける
{Issue番号}があるため、ghでタスク内容を取得できる
# 例: feature/id/123/add-login なら
gh issue view 123
{任意の名称}は短く内容が分かる英数字・ハイフン程度にする（例:add-login,fix-crash-on-launch）
release/{リリースバージョン}/main
- リリース用ブランチ
- バージョン名はプロダクトの慣習に合わせる
- アプリなど semver が明示される場合:
release/v1.0.0/main - 日付ベース等の場合:
release/v2025-12-31/main
- アプリなど semver が明示される場合:
作業手順（名前から内容を読む）
- ブランチ名を上記パターンに当てはめる
feature/id/{n}/...なら Issuenをgh issue view（必要ならリポジトリ指定）で確認するrelease/...なら対象バージョン／日付を読み、リリース作業文脈と捉える- どれにも当てはまらない名前は、慣習外としてユーザーに確認する
作業手順（新規ブランチを付ける）
- 幹線は
mainから切る（特に指示がなければ） - Issue がある作業は
feature/id/{Issue番号}/{短い名称} - リリースラインは
release/{バージョン}/main - Issue 無しの一時作業でも、可能な限り Issue を立ててから feature 名に載せる
ナレッジベース
DO: ブランチ名で種別と Issue を一意に読めるようにする
- 後から
ghや履歴で辿れることが目的である
DO: feature なら先に Issue 番号を確定してから命名する
- 番号無しの
feature/fooは本ルール外になりやすい
DO NOT: main に直接大きな作業を積み続ける前提で進める
- 作業は feature（または release）に切り出す
DO NOT: release 名に曖昧なラベルだけを使う
release/new/mainより、バージョンまたは日付が入った形を優先する
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.
- 9d ago First seen · 89 lines · 173 tokens per session scan A 2623ccaed521
workspace-git-branch-rule is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 173 tokens to every session and 1,103 once invoked, about $0.0009 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
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.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.