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.
git clone --depth 1 https://github.com/YukiMiyatake/costgateWrote 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/rules/yukimiyatake/costgate/git-feature-branch)<a href="https://agentmods.dev/rules/yukimiyatake/costgate/git-feature-branch"><img src="https://agentmods.dev/badge/rules/yukimiyatake/costgate/git-feature-branch/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/rules/yukimiyatake/costgate/git-feature-branch"><img src="https://agentmods.dev/badge/rules/yukimiyatake/costgate/git-feature-branch.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.00404 | $0.00404 |
| Opus 5.5 | $0.00162 | $0.00162 |
| Sonnet 5.5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
git-feature-branch 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.
What it actually says
Git ブランチ運用（CostGate）
必須（エージェント向け）
コミット・push・PR は npm run feat:ship を使う。 Cursor / ローカルは PR 作成まで。CI・レビューコメント・auto-merge は GitHub Actions（ci.yml + pr-automation.yml）が担当。
git add <files>
npm run feat:ship -- --message "日本語のコミットメッセージ"
# マージ待ち + local main 同期（任意）
npm run feat:ship -- -m "…" --wait
# 手動レビュー
npm run feat:ship -- -m "…" --draft
# マージ後に main 同期
npm run feat:sync
mainへの直接 push 禁止（.githooks/pre-push）- コミットメッセージは日本語
- 1 機能 = 1 ブランチ = 1 PR（
main向け） developブランチは使わない
ブランチ開始のみ
npm run feat:start -- short-name
初回セットアップ
npm run hooks:install
リリース
バージョンは repo にコミットしてから tag push。詳細: docs/RELEASE.md
npm run release:version -- 0.6.0 --note "変更概要"
npm run feat:ship -- -m "chore: release v0.6.0"
# マージ後
git tag v0.6.0 && git push origin v0.6.0
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 · 51 lines · 404 tokens per session scan A 4350b97cf6b8
git-feature-branch is a cursor rule published in the GitHub repository YukiMiyatake/costgate (0 stars, last pushed 2mo ago), licensed MIT. It adds 404 tokens to every session, about $0.0016 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 cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.