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/crearize/ai-dev-helm/branch-workflownpx skills add Crearize/ai-dev-helm --skill branch-workflowgit clone --depth 1 https://github.com/Crearize/ai-dev-helmWrote 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/crearize/ai-dev-helm/branch-workflow)<a href="https://agentmods.dev/skills/crearize/ai-dev-helm/branch-workflow"><img src="https://agentmods.dev/badge/skills/crearize/ai-dev-helm/branch-workflow.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.00451 |
| Opus 5 | $0.00015 | $0.00226 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
branch-workflow 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 4d 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
Branch Workflow Skill - ブランチ・Issue作業フロー
禁止事項（最重要）
以下は絶対に禁止。違反は許容されない。
- mainブランチでの直接作業禁止: すべての変更は機能ブランチで行う
- Issue番号なしのブランチ作成禁止: 必ずIssue番号をブランチ名に含める
作業開始前の必須チェック
Step 1: 現在のブランチを確認
git branch --show-current
mainと表示された場合 → 作業禁止！ Step 2へmain以外の場合 → 作業内容とブランチ名が一致しているか確認
Step 2: Issue作成（mainの場合必須）
gh issue create --title "機能名" --body "詳細説明"
Step 3: ブランチ作成
git checkout -b [タイプ]/[作業内容]-[Issue番号]
ブランチ命名規則
| タイプ | 用途 | 例 |
|---|---|---|
feature/ |
新機能開発 | feature/add-login-123 |
fix/ |
バグ修正 | fix/auth-bug-456 |
docs/ |
ドキュメント更新 | docs/update-readme-789 |
refactor/ |
リファクタリング | refactor/user-service-101 |
test/ |
テスト追加・修正 | test/add-api-tests-102 |
PR作成時の必須事項
git commit -m "feat: [機能名]の実装 (closes #[Issue番号])"
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.
- 4d ago First seen · 53 lines · 29 tokens per session scan A 5d464cacf2cc
branch-workflow is a skill published in the GitHub repository Crearize/ai-dev-helm (4 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 451 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…